技術寫作
5624 skills in 文件 > 技術寫作
typescript-type-safety
TypeScript type safety including type guards and advanced type system features. **ALWAYS use when writing ANY TypeScript code (frontend AND backend)** to ensure strict type safety, avoid `any` types, and leverage the type system. Examples - "create function", "implement class", "define interface", "type guard", "discriminated union", "type narrowing", "conditional types", "handle unknown types".
git-commit-workflow
Commit message conventions, staging practices, and commit best practices.Covers conventional commits, explicit staging workflow, logical change grouping,and humble fact-based communication style.Use when user mentions committing changes, writing commit messages, git add,git commit, staging files, or conventional commit format.
python-testing
Python testing with pytest, coverage, fixtures, parametrization, and mocking.Covers test organization, conftest.py, markers, async testing, and TDD workflows.Use when user mentions pytest, unit tests, test coverage, fixtures, mocking,or writing Python tests.
test-driven-development
eXtreme Programming Test-Driven Development (XP-style TDD) Skill. This skill provides both reference documentation AND execution capabilities for the full PLAN -> RED -> GREEN -> REFACTOR workflow.
hardened-outline-driven-development
Automated validation orchestration across proof, spec, type, contract, and test artifacts with configurable precedence and gating. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> EXECUTE -> REPORT workflow.
issue-filing
File framework issues after exhausting other approaches. Document complex problems with multiple failed attempts for framework authors. REQUIRES user permission. Use only after checking docs, community-docs, and trying multiple approaches.
deepwiki-api
This skill enables GitHub repository documentation exploration using DeepWiki API directly via curl. Use when researching repository structure, understanding library APIs, or asking questions about open-source projects. MCP server not required.
dev-swarm-project-restore
Restore a project from 99-archive, a remote git repo, or a local codebase back to the workspace root, including reconstructing missing docs, stages, and sprints. Use when the user asks to resume work on an existing project.
translate-article
Translate MDX articles between English and Japanese for global engineers. Use when the user says "translate this article", "convert to Japanese/English", or asks to localize content in `src/content/docs/`. Auto-detects source language and outputs to the correct i18n path.
c3
This skill should be used when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "audit architecture", "validate C3", or "check C3 docs". Also triggers when no .c3/ directory exists. Routes to c3-query for navigation, c3-alter for changes.
completions
ZSH completion system patterns and conventions. Use when implementing custom completion handling, writing completion files, or working with zsh autocomplete. Do not use when installing packages from homebrew, since that typically installs completions automatically.
obsidian-markdown-structure
Validate and enforce markdown document structure including frontmatter positioning, heading hierarchy, and content organization. Use when creating or validating markdown files.
playwright-testing
Playwright end-to-end testing for web applications. Cross-browser testing (Chromium, Firefox, WebKit),visual regression, API testing, mobile emulation. Use when writing E2E tests, testing across browsers,or setting up automated UI testing workflows.
Global Coding Style
Maintain consistent code formatting, naming conventions, and structure across the entire codebase with automated tools and clear standards. Use this skill when writing any code in any language or framework. When naming variables, functions, classes, or files. When formatting code with proper indentation and line breaks. When refactoring code to remove duplication or extract reusable functions. When running linters or formatters to ensure consistency. When removing dead code, unused imports, or commented-out blocks. When applying DRY principles to avoid code duplication. This skill applies universally to all programming tasks.
idiomatic-rust
Idiomatic Rust patterns for pikru C port. Use when writing or reviewing Rust code ported from C. Don't write C in Rust - the goal is correct behavior, not line-by-line translation.
dgroomes-project-conventions
Conventions and style guidelines for dgroomes' personal projects. Use when upgrading, maintaining, or creating projects in dgroomes' repositories. Covers README style, Gradle configuration, version catalogs, commit messages, and general code conventions.
google-chat-formatting
Convert text to Google Chat compatible formatting (Markdown to Google Chat syntax). Use when formatting messages for Google Chat, converting Markdown documents for Google Chat, or when the user mentions Google Chat formatting.
Global Commenting
Write self-documenting code with clear naming and structure, adding minimal, evergreen comments only when necessary to explain complex logic. Use this skill when writing or reviewing any code that might need comments. When refactoring code to make it more self-explanatory through better naming and structure. When deciding whether to add or remove comments from existing code. When ensuring comments explain why something is done rather than what is being done. When reviewing code to remove outdated or temporary change-related comments. This skill applies to all programming languages and all types of code files.
mcp-deepwiki
This skill provides guidance for using DeepWiki MCP to explore GitHub repository documentation. Use when researching repository structure, understanding library APIs, asking questions about open-source projects, or exploring documentation for any GitHub repository.
code-standards
Expert in code design standards including SOLID principles, Clean Code patterns (KISS, YAGNI, DRY, TDA), and pragmatic software design. **ALWAYS use when designing ANY classes/modules, implementing features, fixing bugs, refactoring code, or writing functions.** Use proactively to ensure proper design, separation of concerns, simplicity, and maintainability. Examples - "create class", "design module", "implement feature", "refactor code", "fix bug", "is this too complex", "apply SOLID", "keep it simple", "avoid over-engineering".