Technical Writing

Electron code signing and notarization workflow for macOS, Windows, and Linux distribution.Anchors:• electron-builder documentation / 適用: Code signing configuration / 目的: Proper certificate management and platform-specific signing• Apple Developer Program / 適用: macOS signing and notarization / 目的: App Store and Gatekeeper compliance• Windows Authenticode / 適用: Windows EV/OV certificate signing / 目的: SmartScreen bypass and user trustTrigger:Use when configuring code signing for Electron apps, setting up certificates for macOS/Windows/Linux, implementing notarization workflows, resolving signing errors, or distributing signed executables.Keywords: code signing, electron-builder, notarization, certificate, macOS signing, Windows Authenticode, entitlements, hardened runtime, EV certificate

ORMベストプラクティスの専門スキル。Drizzle ORMを活用したエンティティ設計、リレーション管理、パフォーマンス最適化を提供します。Anchors:• Designing Data-Intensive Applications (Martin Kleppmann) / 適用: データモデリング / 目的: 型安全なスキーマ定義とパフォーマンス最適化• Drizzle ORM Documentation / 適用: TypeScript ORM / 目的: 型推論とクエリビルダーの活用• High Performance MySQL (Baron Schwartz) / 適用: クエリ最適化 / 目的: N+1問題とインデックス戦略Trigger:Use when defining Drizzle ORM schemas, mapping entity relationships, optimizing database queries, solving N+1 problems, or implementing type-safe data access patterns.ORM, Drizzle, schema, relation, N+1, query builder, type-safe, entity mapping

Upgrades external Claude Skills to factory spec - analyzes existing skill folders and generates missing files, restructures docs, validates compliance

Implement Angular v21 applications with standalone components, signals-based state management, new control flow syntax (@if, @for, @switch), OnPush change detection, inject() DI, Tailwind CSS, and Vitest testing. Use when creating Angular components/services, implementing signals state, writing Vitest tests, applying Tailwind styling, or working with Angular v21 best practices.

多言語ドキュメントと国際化の専門スキル。i18n/l10nベストプラクティス、翻訳準備ライティング、多言語構造設計、グローバルコンテンツ品質保証を提供。Anchors:• The Culture Map (Erin Meyer) / 適用: 文化適応戦略 / 目的: 地域特化ローカライゼーション• Everybody Writes (Ann Handley) / 適用: 翻訳可能コンテンツ作成 / 目的: 明確で翻訳しやすい原文Trigger:Use when designing multilingual documentation, preparing content for translation, implementing i18n frameworks, or validating localization quality.

Use for PLANNING documentation with phased analysis (4 phases), gap identification, and structured knowledge modeling. Best for documentation audits, completeness analysis, and documentation strategy planning. NOT for writing actual docs (use tasks-documentation instead).

Write clear technical documentation following Google's style guide. Use when writing docs, README files, API documentation, code comments, user guides, or asking about documentation style.

Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs

Write behavior-focused tests following Testing Trophy model with real dependencies, avoiding common anti-patterns like testing mocks and polluting production code

Interactive weekly snippets builder for gathering and drafting Friday-Thursday accomplishment summaries. Use when creating weekly snippets, status updates, or accomplishment tracking. Covers context-file creation, source-by-source gathering (Weekly Notes, GitHub PRs/issues, Meeting Notes), section ordering (Ships, Risks, Blockers, Ideas, Collaborations, Shoutouts), business-impact-first writing, and link formatting rules.

Enforces conventional commit message and branch naming conventions with specific prefixes (feat, fix, docs, style, refactor, perf, test, chore). Use when creating git commits, suggesting branch names, reviewing commit messages, or when the user asks about git workflow.

Code quality automation for linting and formatting. Provides ESLint, Prettier, Biome setup, CI/CD integration, pre-commit hooks, and tool migration strategies for consistent code style enforcement.Anchors:• ESLint Official Docs / Apply: Rule configuration, plugin integration / Purpose: Correct API usage and best practices• Prettier Philosophy / Apply: Opinionated formatting / Purpose: Minimize configuration bikeshedding• Biome Performance Model / Apply: Rust-based tooling / Purpose: Optimize development workflow speedTrigger:Use when setting up linting/formatting for new projects, integrating code quality into CI/CD, configuring pre-commit hooks, or migrating between tools.eslint, prettier, biome, lint, format, pre-commit, husky, lint-staged, code quality

BackToBack/ByTheBooks (BTB) - An in-repo collaboration pattern for Human-AI engineering teams. Use this skill when working in repositories with a SPECS/ directory containing README.md, PROGRESS.md, and design documents. BTB emphasizes documentation-driven development, mandatory progress tracking before commits, and a feedback loop between design → MVP → implementation.

Comprehensive guide for building, testing, and distributing Claude Code plugins including slash commands, Agent Skills, subagents, MCP servers, and hooks. Use this when the user asks about creating plugins, writing slash commands, implementing skills, building MCP tools, configuring hooks, plugin architecture, marketplace distribution, or debugging plugin components. Covers 2025 schema with tool permissions, version tracking, and activation triggers.

This skill generates conventional commit messages using AI analysis of staged Git changes. It automatically determines the commit type (feat, fix, docs, etc.), identifies breaking changes, and formats the message according to conventional commit standards. Use this when asked to create a commit message, write a Git commit, or when the user uses the `/commit-smart` or `/gc` command. It is especially useful after changes have been staged with `git add`.

Generates comprehensive documentation templates for open-source and internal projects including README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, LICENSE, and other standard docs with suggested sections and best practices. Use when users request "create project docs", "add OSS documentation", "setup standard docs", or "make it open-source ready".

Use when reviewing pull request changes before providing feedback - analyzes PR with feature-research, presents structured findings, offers user choices for commenting or documentation

SECIモデル（野中郁次郎）に基づく組織知識の形式知化と共有を専門とするスキル。暗黙知（経験、勘、ノウハウ）を形式知（ドキュメント、パターン）に変換し、体系化することで組織全体で再利用可能な知識として活用する。Anchors:• The Knowledge-Creating Company (Nonaka/Takeuchi) / 適用: SECIサイクル4フェーズ（共同化・表出化・連結化・内面化） / 目的: 暗黙知の特定・言語化・統合の理論的基盤• The Pragmatic Programmer (Hunt/Thomas) / 適用: 実践的改善とDRY原則 / 目的: 品質維持と重複知識の統合判断• Design Patterns (Gang of Four) / 適用: パターン記述形式 / 目的: 再利用可能な知識の抽象化と構造化Trigger:Use when formalizing tacit knowledge, documenting best practices, converting code review insights to reusable knowledge, managing organizational knowledge base quality, or applying SECI model workflows.Keywords: knowledge management, tacit knowledge, explicit knowledge, SECI model, documentation, best practices, pattern extraction

Create structured task files for planning dev work. Use when user asks to "create a task", "add a task", "plan a task", or needs to document work items. Creates numbered markdown files in docs/planning/tasks/.

Use when editing, creating, reviewing, or auditing Claude.md files and other Claude documentation - skills, agents, commands, hooks, settings (project .claude/ or personal ~/.claude/). Triggers: "update docs", "save to Claude.md", "document this", pre-commit prompts, contradictions with code, splitting bloated files, creating new Claude.md in undocumented directories.