qte77
187 verified skills187 total stars
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
development1
implementing-rust
Implements concise, streamlined Rust code matching exact architect specifications. Use when writing Rust code, creating modules, or when the user asks to implement features in Rust.
development1
testing-rust
Writes tests following TDD (using cargo test, proptest, and insta) best practices. Use when writing unit tests, integration tests, or property-based tests in Rust.
development1
reviewing-code
Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.
development1
securing-mas
Apply OWASP MAESTRO, MITRE ATLAS, NIST AI RMF, and ISO 42001/23894 security frameworks to MAS designs
development1
scanning-dependencies
Scan project dependencies for vulnerabilities, license issues, and supply chain risks. Use when auditing third-party packages or before releases.
testing1
testing-tdd
Writes tests following TDD Red-Green-Refactor cycle. Language-agnostic methodology with Arrange-Act-Assert structure. Use when implementing features test-first.
development1
testing-tdd
Writes tests following TDD Red-Green-Refactor cycle. Language-agnostic methodology with Arrange-Act-Assert structure. Use when implementing features test-first.
development1
analyzing-contradictions
Detect gaps and contradictions across all prior phases; surface cross-phase tensions, unresolved assumptions, and sales/investor objections. Run after `developing-gtm-strategy` (Phase 4).
development1
analyzing-contradictions
Detect gaps and contradictions across all prior phases; surface cross-phase tensions, unresolved assumptions, and sales/investor objections. Run after `developing-gtm-strategy` (Phase 4).
development1
analyzing-cpp-codebase
Analyzes C++ desktop codebase architecture, dependency graphs, framework detection, and migration assessment. Use when exploring an unfamiliar C++ project or assessing upgrade paths.
development1
analyzing-cpp-codebase
Analyzes C++ desktop codebase architecture, dependency graphs, framework detection, and migration assessment. Use when exploring an unfamiliar C++ project or assessing upgrade paths.
development1
analyzing-source-project
Assess a source project's technical capabilities. Reads `config/sources.md` and produces a structured capability profile. Use to start the GTM pipeline or evaluate technical differentiators (Phase 0).
devops1
auditing-code-security
Audit code against OWASP Top 10 vulnerabilities with structured findings. Use when reviewing code for security issues or conducting security audits.
development1
auditing-code-security
Audit code against OWASP Top 10 vulnerabilities with structured findings. Use when reviewing code for security issues or conducting security audits.
development1
auditing-pcb-design
Runs KiCad DRC/ERC checks, exports gerbers and BOM, and generates a structured findings report. Use when reviewing PCB designs, running design rule checks, or preparing manufacturing outputs.
testing1
auditing-pcb-design
Runs KiCad DRC/ERC checks, exports gerbers and BOM, and generates a structured findings report. Use when reviewing PCB designs, running design rule checks, or preparing manufacturing outputs.
testing1
auditing-readme
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
development1
auditing-readme
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
development1
auditing-readme
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
development1
auditing-website-accessibility
Audits website accessibility for WCAG 2.1 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
development1
auditing-website-accessibility
Audits website accessibility for WCAG 2.1 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
development1
auditing-website-accessibility
Audits website accessibility for WCAG 2.1 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
development1
auditing-website-usability
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
development1
auditing-website-usability
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
development1
auditing-website-usability
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
development1
checking-compliance
Generates compliance requirements from CE/FCC/UL standards for a device description. Use when starting a new embedded product, checking regulatory compliance, or generating initial SYS-REQ entries from applicable directives.
development1
checking-compliance
Generates compliance requirements from CE/FCC/UL standards for a device description. Use when starting a new embedded product, checking regulatory compliance, or generating initial SYS-REQ entries from applicable directives.
development1
checking-compliance
Generates compliance requirements from CE/FCC/UL standards for a device description. Use when starting a new embedded product, checking regulatory compliance, or generating initial SYS-REQ entries from applicable directives.
development1
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
tools1
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
tools1
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
tools1
compacting-context
Compacts verbose context into structured summary. Use after pollution sources (searches, logs, JSON) or at phase milestones.
tools1
compacting-context
Compacts verbose context into structured summary. Use after pollution sources (searches, logs, JSON) or at phase milestones.
tools1
creating-gha
Creates GitHub Actions for the Marketplace. Use when scaffolding a new action, implementing composite steps, writing BATS tests, or preparing a Marketplace release.
testing1
creating-makefile
Scaffold or review Makefiles following org conventions. Use when creating a new Makefile, auditing an existing one, or adding recipes to a project. Auto-detects project type from the working directory.
testing1
creating-makefile
Scaffold or review Makefiles following org conventions. Use when creating a new Makefile, auditing an existing one, or adding recipes to a project. Auto-detects project type from the working directory.
testing1
creating-pr-from-branch
Create a pull request from the current branch. Analyzes commits, generates title+body from PR template, pauses for approval, then pushes and creates PR. Use after committing changes.
tools1
creating-pr-from-branch
Create a pull request from the current branch. Analyzes commits, generates title+body from PR template, pauses for approval, then pushes and creates PR. Use after committing changes.
tools1
designing-backend
Designs concise, streamlined backend systems matching exact task requirements. Use when planning APIs, data models, system architecture, or when the user requests backend design work.
development1
designing-mas-plugins
Design evaluation plugins following 12-Factor + MAESTRO principles
tools1
designing-mas-plugins
Design evaluation plugins following 12-Factor + MAESTRO principles
tools1
detecting-secrets
Detect hardcoded secrets, API keys, tokens, and credentials in code and git history. Use when auditing for leaked secrets or before publishing code.
development1
detecting-secrets
Detect hardcoded secrets, API keys, tokens, and credentials in code and git history. Use when auditing for leaked secrets or before publishing code.
development1
developing-gtm-strategy
Develop customer segmentation, channel selection, and a 90-day launch plan from Phase 2 PMF assessment. Run after `validating-product-market-fit` (Phase 3).
development1
plugins/cc-meta/skills/distilling-plan-learnings
--- name: distilling-plan-learnings description: Extracts decisions, rejected alternatives, and patterns from recent plans into a persistent learnings document. Use after completing a plan or sprint. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Grep, Glob, Edit, Write argument-hint: [time-range] [output-path] context: fork stability: development --- # Plan-to-Learnings Distiller **Target**: $ARGUMENTS Extracts structured learnings from Claude Code plan files.
tools1
plugins/cc-meta/skills/distilling-plan-learnings
--- name: distilling-plan-learnings description: Extracts decisions, rejected alternatives, and patterns from recent plans into a persistent learnings document. Use after completing a plan or sprint. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Grep, Glob, Edit, Write argument-hint: [time-range] [output-path] context: fork stability: development --- # Plan-to-Learnings Distiller **Target**: $ARGUMENTS Extracts structured learnings from Claude Code plan files.
tools1
enforcing-doc-hierarchy
Audit documentation against its declared hierarchy — broken links, duplicates, misplaced content, stale references, single-source-of-truth enforcement. Use for doc health reviews.
testing1
generating-interactive-userstory-md
Build UserStory.md interactively via Q&A. Use when the user wants to create a user story document or start the assisted workflow.
development1
generating-prd-json-from-prd-md
Generates prd.json task tracking file from PRD.md requirements document. Use when initializing Ralph loop or when the user asks to convert PRD to JSON format for autonomous execution.
development1
generating-prd-json-from-prd-md
Generates prd.json task tracking file from PRD.md requirements document. Use when initializing Ralph loop or when the user asks to convert PRD to JSON format for autonomous execution.
development1
generating-prd-md-from-userstory-md
Converts UserStory.md into a structured PRD.md document. Use after generating UserStory.md and before initializing the Ralph loop.
documentation1
generating-prd-md-from-userstory-md
Converts UserStory.md into a structured PRD.md document. Use after generating UserStory.md and before initializing the Ralph loop.
documentation1
generating-prd-md-from-userstory-md
Converts UserStory.md into a structured PRD.md document. Use after generating UserStory.md and before initializing the Ralph loop.
documentation1
plugins/docs-generator/skills/generating-report
--- name: generating-report description: Generates structured reports including status updates, assessments, post-mortems, and executive summaries. Use when writing a report, creating a project status update, or documenting an incident post-mortem. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [report-type] [topic] stability: stable content-hash: sha256:ed0c11638e37e07dcd465265198d17598dbfc1e9fd6c0d764cc288017
tools1
plugins/docs-generator/skills/generating-report
--- name: generating-report description: Generates structured reports including status updates, assessments, post-mortems, and executive summaries. Use when writing a report, creating a project status update, or documenting an incident post-mortem. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [report-type] [topic] stability: stable content-hash: sha256:ed0c11638e37e07dcd465265198d17598dbfc1e9fd6c0d764cc288017
tools1
plugins/docs-generator/skills/generating-report
--- name: generating-report description: Generates structured reports including status updates, assessments, post-mortems, and executive summaries. Use when writing a report, creating a project status update, or documenting an incident post-mortem. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [report-type] [topic] stability: stable content-hash: sha256:ed0c11638e37e07dcd465265198d17598dbfc1e9fd6c0d764cc288017
tools1
generating-slide-deck
Generate an investor or stakeholder presentation from Phase 5 synthesis; produces a structured slide outline with headlines, talking points, and data citations. Run after `synthesizing-research` (Phase 6).
testing1
generating-slide-deck
Generate an investor or stakeholder presentation from Phase 5 synthesis; produces a structured slide outline with headlines, talking points, and data citations. Run after `synthesizing-research` (Phase 6).
testing1
plugins/docs-generator/skills/generating-tech-spec
--- name: generating-tech-spec description: Generates structured technical specifications including ADR (MADR), RFC, design documents, and proposals. Use when writing a spec, creating an ADR, drafting an RFC, or creating a design document. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [spec-type] [topic] stability: stable content-hash: sha256:71c2abb97fa7b7e910c41f19caed62a94b59b49f66730b5aff2e8ef6ebc8a4ee l
tools1
plugins/docs-generator/skills/generating-tech-spec
--- name: generating-tech-spec description: Generates structured technical specifications including ADR (MADR), RFC, design documents, and proposals. Use when writing a spec, creating an ADR, drafting an RFC, or creating a design document. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [spec-type] [topic] stability: stable content-hash: sha256:71c2abb97fa7b7e910c41f19caed62a94b59b49f66730b5aff2e8ef6ebc8a4ee l
tools1
plugins/docs-generator/skills/generating-writeup
--- name: generating-writeup description: Generates academic/technical writeups with IEEE citations and pandoc PDF output. Use when creating research papers, technical reports, or documentation with references. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch argument-hint: [topic] [template] [citation-style] stability: stable content-hash: sha256:9e500bc5e5b4c840c55fdb360e80ad198953af3b1be65784df0f00ae22cbf5ad la
tools1
handing-off-session
Generate structured session handoff notes for cross-session continuity. Use at end of session or when switching context.
tools1
handing-off-session
Generate structured session handoff notes for cross-session continuity. Use at end of session or when switching context.
tools1
handing-off-session
Generate structured session handoff notes for cross-session continuity. Use at end of session or when switching context.
tools1
hardening-codebase
Audit and tighten codebase quality gates — architecture, lint, types, tests, docs, code review. Use when onboarding a project, before a release, or when validation is too permissive.
development1
implementing-document-indexing
Implements document indexing with heading-boundary chunking, embedding, FAISS vector store, and PageIndex-style hybrid retrieval. Use when building RAG pipelines, document search, or memory layers.
development1
implementing-document-indexing
Implements document indexing with heading-boundary chunking, embedding, FAISS vector store, and PageIndex-style hybrid retrieval. Use when building RAG pipelines, document search, or memory layers.
development1
implementing-document-indexing
Implements document indexing with heading-boundary chunking, embedding, FAISS vector store, and PageIndex-style hybrid retrieval. Use when building RAG pipelines, document search, or memory layers.
development1
implementing-firmware
Implements ESP-IDF or PlatformIO firmware with mandatory requirement docstring tags and MISRA-C linting. Use when writing embedded C code, implementing firmware features, or adding requirement-traced functions.
development1
implementing-firmware
Implements ESP-IDF or PlatformIO firmware with mandatory requirement docstring tags and MISRA-C linting. Use when writing embedded C code, implementing firmware features, or adding requirement-traced functions.
development1
implementing-firmware
Implements ESP-IDF or PlatformIO firmware with mandatory requirement docstring tags and MISRA-C linting. Use when writing embedded C code, implementing firmware features, or adding requirement-traced functions.
development1
implementing-go
Implements concise, streamlined Go code matching exact architect specifications. Use when writing Go code, creating packages, or when the user asks to implement features in Go.
development1
implementing-python
Implements concise, streamlined Python code matching exact architect specifications. Use when writing Python code, creating modules, or when the user asks to implement features in Python.
development1
implementing-rust
Implements concise, streamlined Rust code matching exact architect specifications. Use when writing Rust code, creating modules, or when the user asks to implement features in Rust.
development1
implementing-typescript
Implements concise, streamlined TypeScript/React code matching exact architect specifications. Use when writing TypeScript code, creating modules, or when the user asks to implement features in TypeScript/React.
development1
maintaining-agents-md
Maintains AGENTS.md, AGENT_LEARNINGS.md, AGENT_REQUESTS.md, and CONTRIBUTING.md governance files in sync with codebase changes. Use when updating governance files, during sprint reviews, or after structural changes.
development1
maintaining-agents-md
Maintains AGENTS.md, AGENT_LEARNINGS.md, AGENT_REQUESTS.md, and CONTRIBUTING.md governance files in sync with codebase changes. Use when updating governance files, during sprint reviews, or after structural changes.
development1
maintaining-agents-md
Maintains AGENTS.md, AGENT_LEARNINGS.md, AGENT_REQUESTS.md, and CONTRIBUTING.md governance files in sync with codebase changes. Use when updating governance files, during sprint reviews, or after structural changes.
development1
plugins/cc-meta/skills/mining-session-patterns
--- name: mining-session-patterns description: Extract actionable patterns from Claude Code session JSONL files. Surfaces error→fix sequences, tool failure rates, and cost-per-story signals for compound learning. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Glob, Grep, Write argument-hint: [time-range] [output-path] context: fork stability: development --- # Session Pattern Mining **Target**: $ARGUMENTS Mines Claude Code session transcripts for recurring patt
tools1
plugins/cc-meta/skills/mining-session-patterns
--- name: mining-session-patterns description: Extract actionable patterns from Claude Code session JSONL files. Surfaces error→fix sequences, tool failure rates, and cost-per-story signals for compound learning. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Glob, Grep, Write argument-hint: [time-range] [output-path] context: fork stability: development --- # Session Pattern Mining **Target**: $ARGUMENTS Mines Claude Code session transcripts for recurring patt
tools1
plugins/cc-meta/skills/mining-session-patterns
--- name: mining-session-patterns description: Extract actionable patterns from Claude Code session JSONL files. Surfaces error→fix sequences, tool failure rates, and cost-per-story signals for compound learning. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Glob, Grep, Write argument-hint: [time-range] [output-path] context: fork stability: development --- # Session Pattern Mining **Target**: $ARGUMENTS Mines Claude Code session transcripts for recurring patt
tools1
orchestrating-parallel-workers
Fan out tasks to parallel background agents with independent context windows. Use when work can be split into independent units that benefit from isolated execution.
data-ai1
orchestrating-parallel-workers
Fan out tasks to parallel background agents with independent context windows. Use when work can be split into independent units that benefit from isolated execution.
data-ai1
orchestrating-parallel-workers
Fan out tasks to parallel background agents with independent context windows. Use when work can be split into independent units that benefit from isolated execution.
data-ai1
plugins/cc-meta/skills/persisting-bigpicture-learnings
--- name: persisting-bigpicture-learnings description: Persist bigpicture synthesis as dated snapshots in a learnings hub. Maintains latest pointer + append-only archive for cross-session compound learning. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob argument-hint: [input-path] [hub-path] context: inline stability: development --- # Persist Bigpicture to Learnings Hub **Target**: $ARGUMENTS Persists the output of `/synthesizing-cc-bigpicture` as
tools1
plugins/cc-meta/skills/persisting-bigpicture-learnings
--- name: persisting-bigpicture-learnings description: Persist bigpicture synthesis as dated snapshots in a learnings hub. Maintains latest pointer + append-only archive for cross-session compound learning. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob argument-hint: [input-path] [hub-path] context: inline stability: development --- # Persist Bigpicture to Learnings Hub **Target**: $ARGUMENTS Persists the output of `/synthesizing-cc-bigpicture` as
tools1
researching-codebase
Investigates codebase before planning. Use before any non-trivial implementation task to gather context in isolation.
development1
researching-industry-landscape
Map competitive intelligence and industry landscape; produce a competitor map and whitespace analysis. Run alongside `analyzing-source-project` at the start of the GTM pipeline (Phase 1A).
devops1
researching-market
Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
research1
researching-website-design
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
development1
researching-website-design
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
development1
reviewing-code
Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.
development1
reviewing-cpp
Reviews C++ desktop code for memory safety, framework anti-patterns, build system issues, and thread safety. Use when reviewing C++ GUI code quality or when the user asks for code review.
development1
reviewing-cpp
Reviews C++ desktop code for memory safety, framework anti-patterns, build system issues, and thread safety. Use when reviewing C++ GUI code quality or when the user asks for code review.
development1
reviewing-go
Provides concise, focused Go code reviews matching exact task complexity requirements. Use when reviewing Go code quality, concurrency safety, or when the user asks for code review.
development1
reviewing-rust
Provides concise, focused Rust code reviews matching exact task complexity requirements. Use when reviewing Rust code quality, safety, or when the user asks for code review.
development1
reviewing-typescript
Provides concise, focused TypeScript/React code reviews matching exact task complexity requirements. Use when reviewing TypeScript code quality, type safety, or when the user asks for code review.
development1
scanning-dependencies
Scan project dependencies for vulnerabilities, license issues, and supply chain risks. Use when auditing third-party packages or before releases.
testing1
securing-mas
Apply OWASP MAESTRO, MITRE ATLAS, NIST AI RMF, and ISO 42001/23894 security frameworks to MAS designs
development1
securing-mas
Apply OWASP MAESTRO, MITRE ATLAS, NIST AI RMF, and ISO 42001/23894 security frameworks to MAS designs
development1
summarizing-session-end
Auto-generates a session summary on SessionEnd. Writes structured notes to ~/.claude/session-summaries/ for use by bigpicture synthesis.
documentation1
summarizing-session-end
Auto-generates a session summary on SessionEnd. Writes structured notes to ~/.claude/session-summaries/ for use by bigpicture synthesis.
documentation1
summarizing-session-end
Auto-generates a session summary on SessionEnd. Writes structured notes to ~/.claude/session-summaries/ for use by bigpicture synthesis.
documentation1
plugins/cc-meta/skills/synthesizing-cc-bigpicture
--- name: synthesizing-cc-bigpicture description: Synthesizes a living big-picture meta-plan from Claude Code sessions, plans, tasks, and team communications. Use when orienting across projects, assessing reasoning modes, or creating a plan-to-plan overview. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Grep, Glob argument-hint: [project-name] [time-range] [output-path] context: fork --- # Big-Picture Synthesis **Target**: $ARGUMENTS Synthesizes a **plan to plan
tools1
synthesizing-research
Synthesize all prior research into a unified GTM narrative. Run after `analyzing-contradictions` to prepare for slide deck generation (Phase 5).
research1
synthesizing-research
Synthesize all prior research into a unified GTM narrative. Run after `analyzing-contradictions` to prepare for slide deck generation (Phase 5).
research1
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
development1
testing-python
Writes tests following TDD Red-Green-Refactor (pytest + Hypothesis). Tests behavior, not implementation. Use when writing unit tests, integration tests, or property tests.
development1
testing-python
Writes tests following TDD Red-Green-Refactor (pytest + Hypothesis). Tests behavior, not implementation. Use when writing unit tests, integration tests, or property tests.
development1
testing-typescript
Writes tests following TDD (using vitest and @testing-library/react) best practices. Use when writing unit tests, integration tests, or component tests in TypeScript.
development1
testing-typescript
Writes tests following TDD (using vitest and @testing-library/react) best practices. Use when writing unit tests, integration tests, or component tests in TypeScript.
development1
tracing-requirements
Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags. Use when checking requirement coverage, finding orphaned code, or generating a coverage matrix.
development1
validating-product-market-fit
Score product-market fit from Phase 1B market analysis; produce PMF score, evidence matrix, and risk register. Run after `researching-market` (Phase 2).
research1
writing-readme
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
documentation1
creating-gha
Creates GitHub Actions for the Marketplace. Use when scaffolding a new action, implementing composite steps, writing BATS tests, or preparing a Marketplace release.
testing1
researching-industry-landscape
Map competitive intelligence and industry landscape; produce a competitor map and whitespace analysis. Run alongside `analyzing-source-project` at the start of the GTM pipeline (Phase 1A).
devops1
researching-market
Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
research1
creating-pr-from-branch
Create a pull request from the current branch. Analyzes commits, generates title+body from PR template, pauses for approval, then pushes and creates PR. Use after committing changes.
tools1
implementing-cpp
Implements C++17 desktop GUI code with wxWidgets, GTK3, or Qt framework patterns and CMake build system. Use when writing C++ desktop application code, creating GUI components, or implementing framework-specific features.
development1
enforcing-doc-hierarchy
Audit documentation against its declared hierarchy — broken links, duplicates, misplaced content, stale references, single-source-of-truth enforcement. Use for doc health reviews.
testing1
creating-gha
Creates GitHub Actions for the Marketplace. Use when scaffolding a new action, implementing composite steps, writing BATS tests, or preparing a Marketplace release.
testing1
creating-makefile
Scaffold or review Makefiles following org conventions. Use when creating a new Makefile, auditing an existing one, or adding recipes to a project. Auto-detects project type from the working directory.
testing1
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
development1
reviewing-go
Provides concise, focused Go code reviews matching exact task complexity requirements. Use when reviewing Go code quality, concurrency safety, or when the user asks for code review.
development1
developing-gtm-strategy
Develop customer segmentation, channel selection, and a 90-day launch plan from Phase 2 PMF assessment. Run after `validating-product-market-fit` (Phase 3).
development1
designing-mas-plugins
Design evaluation plugins following 12-Factor + MAESTRO principles
tools1
testing-rust
Writes tests following TDD (using cargo test, proptest, and insta) best practices. Use when writing unit tests, integration tests, or property-based tests in Rust.
development1
reviewing-rust
Provides concise, focused Rust code reviews matching exact task complexity requirements. Use when reviewing Rust code quality, safety, or when the user asks for code review.
development1
implementing-rust
Implements concise, streamlined Rust code matching exact architect specifications. Use when writing Rust code, creating modules, or when the user asks to implement features in Rust.
development1
testing-tdd
Writes tests following TDD Red-Green-Refactor cycle. Language-agnostic methodology with Arrange-Act-Assert structure. Use when implementing features test-first.
development1
scanning-dependencies
Scan project dependencies for vulnerabilities, license issues, and supply chain risks. Use when auditing third-party packages or before releases.
testing1
writing-readme
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
documentation1
implementing-typescript
Implements concise, streamlined TypeScript/React code matching exact architect specifications. Use when writing TypeScript code, creating modules, or when the user asks to implement features in TypeScript/React.
development1
auditing-code-security
Audit code against OWASP Top 10 vulnerabilities with structured findings. Use when reviewing code for security issues or conducting security audits.
development1
implementing-python
Implements concise, streamlined Python code matching exact architect specifications. Use when writing Python code, creating modules, or when the user asks to implement features in Python.
development1
implementing-cpp
Implements C++17 desktop GUI code with wxWidgets, GTK3, or Qt framework patterns and CMake build system. Use when writing C++ desktop application code, creating GUI components, or implementing framework-specific features.
development1
reviewing-rust
Provides concise, focused Rust code reviews matching exact task complexity requirements. Use when reviewing Rust code quality, safety, or when the user asks for code review.
development1
researching-website-design
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
development1
testing-rust
Writes tests following TDD (using cargo test, proptest, and insta) best practices. Use when writing unit tests, integration tests, or property-based tests in Rust.
development1
reviewing-code
Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.
development1
reviewing-go
Provides concise, focused Go code reviews matching exact task complexity requirements. Use when reviewing Go code quality, concurrency safety, or when the user asks for code review.
development1
tracing-requirements
Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags. Use when checking requirement coverage, finding orphaned code, or generating a coverage matrix.
development1
enforcing-doc-hierarchy
Audit documentation against its declared hierarchy — broken links, duplicates, misplaced content, stale references, single-source-of-truth enforcement. Use for doc health reviews.
testing1
plugins/docs-generator/skills/generating-tech-spec
--- name: generating-tech-spec description: Generates structured technical specifications including ADR (MADR), RFC, design documents, and proposals. Use when writing a spec, creating an ADR, drafting an RFC, or creating a design document. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [spec-type] [topic] stability: stable content-hash: sha256:71c2abb97fa7b7e910c41f19caed62a94b59b49f66730b5aff2e8ef6ebc8a4ee l
tools1
plugins/cc-meta/skills/distilling-plan-learnings
--- name: distilling-plan-learnings description: Extracts decisions, rejected alternatives, and patterns from recent plans into a persistent learnings document. Use after completing a plan or sprint. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Grep, Glob, Edit, Write argument-hint: [time-range] [output-path] context: fork stability: development --- # Plan-to-Learnings Distiller **Target**: $ARGUMENTS Extracts structured learnings from Claude Code plan files.
tools1
detecting-secrets
Detect hardcoded secrets, API keys, tokens, and credentials in code and git history. Use when auditing for leaked secrets or before publishing code.
development1
implementing-python
Implements concise, streamlined Python code matching exact architect specifications. Use when writing Python code, creating modules, or when the user asks to implement features in Python.
development1
plugins/docs-generator/skills/generating-writeup
--- name: generating-writeup description: Generates academic/technical writeups with IEEE citations and pandoc PDF output. Use when creating research papers, technical reports, or documentation with references. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch argument-hint: [topic] [template] [citation-style] stability: stable content-hash: sha256:9e500bc5e5b4c840c55fdb360e80ad198953af3b1be65784df0f00ae22cbf5ad la
tools1
reviewing-cpp
Reviews C++ desktop code for memory safety, framework anti-patterns, build system issues, and thread safety. Use when reviewing C++ GUI code quality or when the user asks for code review.
development1
plugins/cc-meta/skills/synthesizing-cc-bigpicture
--- name: synthesizing-cc-bigpicture description: Synthesizes a living big-picture meta-plan from Claude Code sessions, plans, tasks, and team communications. Use when orienting across projects, assessing reasoning modes, or creating a plan-to-plan overview. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Grep, Glob argument-hint: [project-name] [time-range] [output-path] context: fork --- # Big-Picture Synthesis **Target**: $ARGUMENTS Synthesizes a **plan to plan
tools1
plugins/cc-meta/skills/persisting-bigpicture-learnings
--- name: persisting-bigpicture-learnings description: Persist bigpicture synthesis as dated snapshots in a learnings hub. Maintains latest pointer + append-only archive for cross-session compound learning. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob argument-hint: [input-path] [hub-path] context: inline stability: development --- # Persist Bigpicture to Learnings Hub **Target**: $ARGUMENTS Persists the output of `/synthesizing-cc-bigpicture` as
tools1
designing-backend
Designs concise, streamlined backend systems matching exact task requirements. Use when planning APIs, data models, system architecture, or when the user requests backend design work.
development1
compacting-context
Compacts verbose context into structured summary. Use after pollution sources (searches, logs, JSON) or at phase milestones.
tools1
analyzing-source-project
Assess a source project's technical capabilities. Reads `config/sources.md` and produces a structured capability profile. Use to start the GTM pipeline or evaluate technical differentiators (Phase 0).
devops1
developing-gtm-strategy
Develop customer segmentation, channel selection, and a 90-day launch plan from Phase 2 PMF assessment. Run after `validating-product-market-fit` (Phase 3).
development1
analyzing-contradictions
Detect gaps and contradictions across all prior phases; surface cross-phase tensions, unresolved assumptions, and sales/investor objections. Run after `developing-gtm-strategy` (Phase 4).
development1
synthesizing-research
Synthesize all prior research into a unified GTM narrative. Run after `analyzing-contradictions` to prepare for slide deck generation (Phase 5).
research1
researching-industry-landscape
Map competitive intelligence and industry landscape; produce a competitor map and whitespace analysis. Run alongside `analyzing-source-project` at the start of the GTM pipeline (Phase 1A).
devops1
researching-market
Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
research1
writing-readme
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
documentation1
researching-codebase
Investigates codebase before planning. Use before any non-trivial implementation task to gather context in isolation.
development1
designing-backend
Designs concise, streamlined backend systems matching exact task requirements. Use when planning APIs, data models, system architecture, or when the user requests backend design work.
development1
plugins/docs-generator/skills/generating-writeup
--- name: generating-writeup description: Generates academic/technical writeups with IEEE citations and pandoc PDF output. Use when creating research papers, technical reports, or documentation with references. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch argument-hint: [topic] [template] [citation-style] stability: stable content-hash: sha256:9e500bc5e5b4c840c55fdb360e80ad198953af3b1be65784df0f00ae22cbf5ad la
tools1
plugins/cc-meta/skills/synthesizing-cc-bigpicture
--- name: synthesizing-cc-bigpicture description: Synthesizes a living big-picture meta-plan from Claude Code sessions, plans, tasks, and team communications. Use when orienting across projects, assessing reasoning modes, or creating a plan-to-plan overview. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Grep, Glob argument-hint: [project-name] [time-range] [output-path] context: fork --- # Big-Picture Synthesis **Target**: $ARGUMENTS Synthesizes a **plan to plan
tools1
implementing-go
Implements concise, streamlined Go code matching exact architect specifications. Use when writing Go code, creating packages, or when the user asks to implement features in Go.
development1
analyzing-cpp-codebase
Analyzes C++ desktop codebase architecture, dependency graphs, framework detection, and migration assessment. Use when exploring an unfamiliar C++ project or assessing upgrade paths.
development1
validating-product-market-fit
Score product-market fit from Phase 1B market analysis; produce PMF score, evidence matrix, and risk register. Run after `researching-market` (Phase 2).
research1
generating-interactive-userstory-md
Build UserStory.md interactively via Q&A. Use when the user wants to create a user story document or start the assisted workflow.
development1
testing-python
Writes tests following TDD Red-Green-Refactor (pytest + Hypothesis). Tests behavior, not implementation. Use when writing unit tests, integration tests, or property tests.
development1
implementing-go
Implements concise, streamlined Go code matching exact architect specifications. Use when writing Go code, creating packages, or when the user asks to implement features in Go.
development1
reviewing-typescript
Provides concise, focused TypeScript/React code reviews matching exact task complexity requirements. Use when reviewing TypeScript code quality, type safety, or when the user asks for code review.
development1
testing-typescript
Writes tests following TDD (using vitest and @testing-library/react) best practices. Use when writing unit tests, integration tests, or component tests in TypeScript.
development1
reviewing-typescript
Provides concise, focused TypeScript/React code reviews matching exact task complexity requirements. Use when reviewing TypeScript code quality, type safety, or when the user asks for code review.
development1
validating-product-market-fit
Score product-market fit from Phase 1B market analysis; produce PMF score, evidence matrix, and risk register. Run after `researching-market` (Phase 2).
research1
analyzing-source-project
Assess a source project's technical capabilities. Reads `config/sources.md` and produces a structured capability profile. Use to start the GTM pipeline or evaluate technical differentiators (Phase 0).
devops1
generating-interactive-userstory-md
Build UserStory.md interactively via Q&A. Use when the user wants to create a user story document or start the assisted workflow.
development1
hardening-codebase
Audit and tighten codebase quality gates — architecture, lint, types, tests, docs, code review. Use when onboarding a project, before a release, or when validation is too permissive.
development1
tracing-requirements
Validates the SYS→PRD→SW requirement traceability chain by reconciling database entries with code docstring tags. Use when checking requirement coverage, finding orphaned code, or generating a coverage matrix.
development1
implementing-typescript
Implements concise, streamlined TypeScript/React code matching exact architect specifications. Use when writing TypeScript code, creating modules, or when the user asks to implement features in TypeScript/React.
development1
auditing-pcb-design
Runs KiCad DRC/ERC checks, exports gerbers and BOM, and generates a structured findings report. Use when reviewing PCB designs, running design rule checks, or preparing manufacturing outputs.
testing1
committing-staged-with-message
Generate commit message for staged changes, pause for approval, then commit. Stage files first with `git add`, then run this skill.
tools1
implementing-cpp
Implements C++17 desktop GUI code with wxWidgets, GTK3, or Qt framework patterns and CMake build system. Use when writing C++ desktop application code, creating GUI components, or implementing framework-specific features.
development1
hardening-codebase
Audit and tighten codebase quality gates — architecture, lint, types, tests, docs, code review. Use when onboarding a project, before a release, or when validation is too permissive.
development1
generating-slide-deck
Generate an investor or stakeholder presentation from Phase 5 synthesis; produces a structured slide outline with headlines, talking points, and data citations. Run after `synthesizing-research` (Phase 6).
testing1
researching-codebase
Investigates codebase before planning. Use before any non-trivial implementation task to gather context in isolation.
development1
generating-prd-json-from-prd-md
Generates prd.json task tracking file from PRD.md requirements document. Use when initializing Ralph loop or when the user asks to convert PRD to JSON format for autonomous execution.
development1