文件

Write comprehensive test coverage across unit, integration, regression, end-to-end, and manual tests. Watch for deprecation warnings in test output and address them immediately. Use when writing tests, implementing features, or before creating pull requests.

Use when planning software development tasks, before writing code or implementation plans - refines rough technical ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. For software architecture, components, data flow, and technical design decisions. Don't use during clear 'mechanical' coding processes

Reference and maintain documentation of the project's technical stack including frameworks, languages, databases, testing tools, and third-party services. Use this skill when choosing technologies for implementation, adding new dependencies or libraries, setting up project infrastructure, configuring build tools and package managers, integrating third-party services (authentication, email, monitoring), selecting appropriate frameworks for features, ensuring consistency with existing technology choices, documenting technology decisions, reviewing technology compatibility, or onboarding team members to the tech stack. Apply this skill when making technology decisions, adding new tools or services, documenting the stack, or ensuring new code aligns with the project's established technical architecture.

Execute tests following TDD cycle: RED (verify test fails) → GREEN (implement to pass) → REFACTOR.Interprets tests.json and performs steps using available tools (browser MCP, API, CLI, etc.).WHEN TO USE:- Starting implementation of a ticket with TDD: yes- After writing test spec (3-spec.md) and tests.json- When user says "run tests", "test this", "TDD cycle"- After fixing a failing testREQUIRES:- Ticket with 3-spec.md- tests.json in .pmc/docs/tests/tickets/T0000N/

Automatically retrieve relevant information from the organization's CustomGPT.ai knowledge base when answering questions about documented topics, policies, procedures, or technical specifications.

Managing complexity is software's primary technical imperative - all other goals are secondary

Generate high-quality, "All-Star" README files for open-source repositories. Use this skill when a user asks to create, update, or improve a README.md file for their project.

Git best practices for commits, merges, and collaboration. Use when writing commit messages, deciding between merge/rebase, handling merge conflicts, or following git workflows.

RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes

Generate clear Conventional Commit messages from git diffs; use when writing commits, reviewing staged work, or when the user requests a commit.

BANKSY spatial transcriptomics analysis tool - complete documentation with notebooks and source code

Build Claude Code extensions - skills, agents, hooks, plugins, marketplaces, slash commands. Use when creating Claude Code components, building new skills, writing agents, creating hooks, making plugins, setting up marketplaces, writing slash commands, fixing extension configurations, or troubleshooting Claude Code extensions. Includes builder agents for autonomous creation. Not for looking up docs - use claude-code-docs-reference for that.

Create Architecture Decision Records (ADRs) documenting significant technical decisions for the FF Analytics platform. This skill should be used when making architectural choices, evaluating alternatives for data models or infrastructure, documenting trade-offs, or when the user asks "should we use X or Y approach?" Guides through the ADR creation workflow from context gathering to documentation.

Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes

CellChat cell-cell communication analysis toolkit - complete documentation with precise file name-based categorization

Foundational knowledge for writing Stan 2.37 models including program structure, type system, distributions, and best practices. Use when creating or reviewing Stan models.

Automated documentation generation specialist for technical specs, API docs, user guides, and knowledge bases with multi-format output

TypeScript development best practices, code quality tools, and documentation templates. Activated when working with .ts, .tsx files or TypeScript projects.

Write effective tests with proper structure and coverage. Use when writing unit tests, integration tests, or improving test quality.

Use after writing-plans to decompose monolithic plan into individual task files and identify tasks that can run in parallel (up to 2 subagents simultaneously)