all publishers

compozy

@compozy source repo

311 published skills · page 1 of 4

  1. ▌
    To Prompt 2 · compozy bundle
    Create a handoff brief for another LLM to implement. Preserve accepted decisions and write to docs/prompts/; excludes one-shot questions and end-user copy.
    2.9k repo stars
  2. ▌
    Turborepo 2 · compozy bundle
    Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
    2.9k repo stars
  3. ▌
    QA Execution 2 · compozy bundle
    Run requested dogfooding through public product interfaces. Use existing QA journeys or qa-report to plan them; excludes routine code edits and CI-only verification.
    2.9k repo stars
  4. ▌
    Writing Skills 2 · compozy bundle
    Create, refactor, or debug agent skills and their loading. Use writing-agents-md for AGENTS.md/CLAUDE.md; excludes general docs and READMEs.
    2.9k repo stars
  5. ▌
    Writing Agents Md 2 · compozy
    Write or audit AGENTS.md/CLAUDE.md instructions. Use writing-skills for on-demand skills; excludes human-facing docs and READMEs.
    2.9k repo stars
  6. ▌
    Writing Tech Post 2 · compozy bundle
    Write or edit engineering posts with supported claims. Use for drafts, rewrites, and publication reviews; excludes marketing pages, API references, release notes, and internal specs.
    2.9k repo stars
  7. ▌
    Git Rebase 2 · compozy bundle
    Rebase branches and resolve cross-commit conflicts while preserving changes. Excludes merge-commit workflows, cherry-picking, and repository setup.
    2.9k repo stars
  8. ▌
    Cy Create Spec 2 · compozy bundle
    Create or update a requested CompozyOS spec and its applicable companion contracts, reusing current decisions and research. Not a prerequisite for ordinary coding tasks.
    2.9k repo stars
  9. ▌
    Eng Delivery · compozy
    Deliver work in the compozy/compozy repository. Use when dispatching or supervising sessions, opening or updating a PR, filing an issue, handling review feedback or CI, or declaring work done. Excludes product behavior of the shipped spec-cycle agents.
    2.9k repo stars
  10. ▌
    Cy Orquestrate Issue · compozy bundle
    Orchestrate GitHub bug resolution through a new CompozyOS managed worktree and Claude Opus 5.5 Medium session per issue. Investigate reported bugs, create missing issues, and dispatch an executor responsible for a detailed PR, green CI, and all CodeRabbit and Greptile feedback. Use when asked to delegate issue resolution; excludes spec task graphs, direct implementation, and review-only work on an existing PR.
    2.9k repo stars
  11. ▌
    Better UI · compozy bundle
    Polishes and improves the UI in your project. Covers concentric border radius, optical alignment, surface depth, contextual icons, hit areas and more.
    2.9k repo stars
  12. ▌
    Git Rebase · compozy bundle
    Rebase branches and resolve cross-commit conflicts while preserving changes. Excludes merge-commit workflows, cherry-picking, and repository setup.
    2.9k repo stars
  13. ▌
    Tech Logos · compozy
    Reuse or add official company, provider, and social-platform logos, including placeholders and landing/auth/integration UIs. Use the existing brand inventory. Excludes custom logos, generic icon libraries, and marketing imagery.
    2.9k repo stars
  14. ▌
    Deep Review · compozy bundle
    Review branch diffs, working trees, or PRs in depth with defect, polish and cross-contract coverage. Includes incremental and spec-conformance reviews; excludes fixes, spec-document reviews and quick single-file feedback.
    2.9k repo stars
  15. ▌
    Tailwindcss · compozy bundle
    Style components with Tailwind CSS v4 and project tokens. Excludes plain CSS, CSS-in-JS, and other utility frameworks.
    2.9k repo stars
  16. ▌
    Skill Doctor · compozy bundle
    Grades agent skills by scoring agent conversations against efficiency and code-quality rubrics, then drafts concrete skill edits and a shareable report. Use when the user wants their agent setup graded from real conversation history, or asks which of their installed skills are actually working.
    2.9k repo stars
  17. ▌
    Better Colors · compozy bundle
    Helps you build a color system and answer anything about color in your project. You can generate palettes, use semantic tokens, convert between formats, check contrast and more.
    2.9k repo stars
  18. ▌
    Better Layout · compozy bundle
    Helps with grouping, alignment, reading order, progressive disclosure and other details that make a good layout.
    2.9k repo stars
  19. ▌
    Humanizer · compozy bundle
    Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer
    2.9k repo stars
  20. ▌
    Turborepo · compozy bundle
    Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
    2.9k repo stars
  21. ▌
    Writing Agents Md · compozy
    Write or audit AGENTS.md/CLAUDE.md instructions. Use writing-skills for on-demand skills; excludes human-facing docs and READMEs.
    2.9k repo stars
  22. ▌
    Tanstack 2 · compozy bundle
    Implement React data, routes, or forms with TanStack. Covers Query, Router, and Form; excludes Start, DB, and unrelated state or routing libraries.
    2.9k repo stars
  23. ▌
    UI Craft 2 · compozy bundle
    Design, build, review, or refactor visible UI, including pages, components, forms, loading/error states, and AI chat/streaming interfaces. Excludes backend, infrastructure, CLI/TUI, and docs-only work.
    2.9k repo stars
  24. ▌
    Use Modern Go · compozy bundle
    Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
    2.9k repo stars
  25. ▌
    Eng Design · compozy
    Compozy visual-design authority for production UI, static artifacts, prototypes, and reviews. Use when creating or reviewing a Compozy surface or changing tokens, typography, spacing, depth, icons, or motion. Do not use for capture-only verification; use eng-ui-screenshot.
    2.9k repo stars
  26. ▌
    Cy Issue To Spec · compozy bundle
    Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.
    2.9k repo stars
  27. ▌
    Better Typography · compozy bundle
    Focuses on type scale, spacing, sizing, variable fonts, OpenType features, wrapping, truncation and other details that make typography feel great across your product.
    2.9k repo stars
  28. ▌
    Storybook Stories · compozy bundle
    Create, update, refactor, or troubleshoot Storybook stories using project conventions. Excludes component implementation, token changes, E2E browser tests, and other documentation.
    2.9k repo stars
  29. ▌
    App Renderer Systems · compozy bundle
    Create, extend, or debug frontend domain modules organized under systems/. Covers adapters, Query hooks, local state, and public exports; excludes generic components and backend implementation.
    2.9k repo stars
  30. ▌
    Better Accessibility · compozy bundle
    Helps your project comply with accessibility standards and best practices.
    2.9k repo stars
  31. ▌
    Eng QA Bootstrap · compozy bundle
    Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA. Use when local QA needs daemon, workspace, provider, or playbook setup. Do not use for unit tests, planning-only work, or browser-only checks.
    2.9k repo stars
  32. ▌
    Eng Code Guidelines · compozy bundle
    Go production discipline for Compozy. Use when writing or editing non-test Go files under cmd or internal, including config, logging, CLI, concurrency, and process-lifecycle paths. Do not use for Go tests; pair it with the narrower schema, contract, or cleanup skill when those domains apply.
    2.9k repo stars
  33. ▌
    Eng Real Scenario QA · compozy bundle
    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit. Use for release or complex-integration QA. Do not use for smoke, static, mock-only, or unit-test work.
    2.9k repo stars
  34. ▌
    Eng Schema Migration · compozy bundle
    Change Compozy SQLite tables, columns, indexes, constraints, triggers, or seed data under internal/store using append-only Goose migrations and owning generators. Excludes in-memory structures and non-SQLite caches.
    2.9k repo stars
  35. ▌
    Eng Test Conventions · compozy bundle
    Go test-shape discipline for Compozy. Use when writing or editing *_test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.
    2.9k repo stars
  36. ▌
    Eng Worktree Isolation · compozy bundle
    Isolates Compozy runtime state for concurrent worktrees and QA runs. Use when another agent or runtime may share the machine, or when creating a parallel worktree. Do not use for single-worktree or build-only work.
    2.9k repo stars
  37. ▌
    Eng Contract Codegen Coship · compozy bundle
    Contract co-ship for Compozy wire changes. Use when editing public DTOs, OpenAPI, JSON-RPC extension shapes, generated clients, or handler request/response semantics. Do not use for internal Go refactors or test-only changes that leave the wire contract unchanged.
    2.9k repo stars
  38. ▌
    Compozy · compozy bundle
    Operate CompozyOS. Use when working with CompozyOS sessions, agents, native tools, skills, tasks, Loops, Goals, Terminal, desktops and windows, automation, extensions, or configuration. Don't use for unrelated projects.
    2.9k repo stars
  39. ▌
    Remotion Render · compozy bundle
    Export a Remotion video
    2.9k repo stars
  40. ▌
    Remotion Studio · compozy bundle
    Preview a Remotion video
    2.9k repo stars
  41. ▌
    Remotion Upgrade · compozy bundle
    Upgrade Remotion, and related packages
    2.9k repo stars
  42. ▌
    Remotion Captions · compozy bundle
    Transcribing, displaying and animating captions
    2.9k repo stars
  43. ▌
    Remotion Multimedia · compozy bundle
    Interacting with Mediabunny
    2.9k repo stars
  44. ▌
    Remotion Interactivity · compozy bundle
    Structure Remotion markup for interactivity
    2.9k repo stars
  45. ▌
    Open Design · compozy bundle
    Create or refine interfaces, sites, HTML slides, and visual documents from a short brief, existing design, or _uiux.md, as directly openable HTML or as prototypes built with the project's own component library. Use for design artifacts and prototypes; excludes production application implementation and automatic independent review.
    2.9k repo stars
  46. ▌
    Open Design Setup · compozy bundle
    Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and production feature implementation.
    2.9k repo stars
  47. ▌
    Open Design Review · compozy
    Run the explicitly requested independent review and refinement cycle for an OpenDesign HTML artifact or library prototype through the native open-design-review loop. Use for a new brief or existing docs/design artifacts; ordinary edits and _uiux.md input alone do not trigger it.
    2.9k repo stars
  48. ▌
    Open Design Browser · compozy
    Inspect and exercise local HTML design artifacts and library prototype previews with the existing agent-browser CLI, including screenshots, interaction checks, and rendered DOM snapshots. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser automation.
    2.9k repo stars
  49. ▌
    Remotion Docs · compozy bundle
    Search Remotion documentation
    2.9k repo stars
  50. ▌
    Remotion Maps · compozy bundle
    Remotion Map animation knowledge
    2.9k repo stars
  51. ▌
    Remotion Saas · compozy bundle
    Build an app with Remotion
    2.9k repo stars
  52. ▌
    Remotion Create · compozy bundle
    Create a new Remotion video
    2.9k repo stars
  53. ▌
    Remotion Markup · compozy bundle
    Content, animation and effects best practices
    2.9k repo stars
  54. ▌
    Proto · compozy bundle
    Author, set up and debug @compozy/proto prototypes, drafts, flows, existing Storybook stories and the canvas. Use when editing `*.proto.tsx`, `src/drafts/`, `*.flow.ts`, `proto.canvas.tsx` or `proto.config.ts` and its Vite, Storybook or Vitest guards, when running the `proto` CLI or MCP tools, or when `proto check`, `proto dev` or a capture fails. Not for UI edits that touch no prototype, nor for gallery review comments (proto-apply-comments).
    2.9k repo stars
  55. ▌
    Cy Release Video · compozy bundle
    Create or revise CompozyOS release videos with high-resolution product captures, Ultramock camera scenes, and the reusable Remotion package. Excludes publishing tweets and general video editing.
    2.9k repo stars
  56. ▌
    Proto Apply Comments · compozy
    Apply @compozy/proto gallery review comments to the code that renders them, verify the reviewed state and answer each thread. Use for a comment id such as `login-form-7` or `flow-checkout-2` or `story--ui-button-3`, a gallery link with `comment=`, or a request to address open prototype review comments. For authoring prototypes or setting up proto, use the proto skill.
    2.9k repo stars
  57. ▌
    Performance Optimization · compozy bundle
    Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
    2.9k repo stars
  58. ▌
    Git Rebase 4 · compozy bundle
    Intelligently handle git rebase operations and resolve merge conflicts while preserving features and maintaining code quality. Use when rebasing feature branches, resolving conflicts across commits, and ensuring clean linear history without losing changes.
    2.9k repo stars
  59. ▌
    Compozy 4 · compozy bundle
    Explains Compozy capabilities, CLI commands, core workflow skills, optional extension skills, configuration, artifact structure, reusable agents, and extensions. Use when the user asks how to use Compozy, what commands are available, how the workflow pipeline works, or how to configure a workspace. Do not use for executing workflow steps — use the specific cy- skills instead.
    2.9k repo stars
  60. ▌
    Cy Create Tasks 6 · compozy bundle
    Decomposes PRDs and TechSpecs into detailed, independently implementable task files with enrichment from codebase exploration. Use when a PRD or TechSpec exists and needs to be broken down into executable tasks, or when task files need enrichment with implementation context. Do not use for PRD creation, TechSpec generation, or direct task execution.
    2.9k repo stars
  61. ▌
    Cy Execute Task 4 · compozy bundle
    Executes one PRD task end-to-end using a provided task file, PRD directory, tracking file paths, and auto-commit mode. Use when a prompt includes a task specification that must be implemented, validated, and reflected in task tracking files. Do not use for PR review batches, generic coding tasks without a PRD task file, or standalone verification-only work.
    2.9k repo stars
  62. ▌
    Cy Spec Preflight 4 · compozy bundle
    Loads the AGH spec authoring playbook plus relevant lessons, standing directives, glossary, and active context before cy-create-prd, cy-create-techspec, or cy-create-tasks runs. Applies phase-specific checks: PRDs stay business-focused, TechSpecs carry the six quality markers, and every spec/task captures extensibility integration, agent-manageability, config lifecycle, QA tail coverage, and Web/Docs Impact. Use whenever an AGH spec authoring skill is about to run. Do not use for spec execution, review remediation, or non-spec brainstorming output.
    2.9k repo stars
  63. ▌
    Cy Spec Peer Review 4 · compozy bundle
    Runs an optional cross-LLM peer review of a TechSpec via compozy exec --ide claude --model opus --reasoning-effort xhigh and packages findings for user-directed incorporation. Use when a TechSpec draft has already been approved by the user and they want an external review round, especially for autonomy/network/memory-impacting designs. Do not use for PRDs, automatic approval gates, code review batches, or auto-looped review cycles.
    2.9k repo stars
  64. ▌
    Cy Final Verify 6 · compozy
    Enforces fresh verification evidence before any completion, fix, or passing claim, and before commits or PR creation. Use when an agent is about to report success, hand off work, or commit code. Do not use for early planning, brainstorming, or tasks that have not yet reached a concrete verification step.
    2.9k repo stars
  65. ▌
    Cy Review Round 4 · compozy bundle
    Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with cy-fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.
    2.9k repo stars
  66. ▌
    Refactoring Analysis 4 · compozy bundle
    Analyzes codebases to identify refactoring opportunities based on Martin Fowler's catalog of code smells and refactoring techniques. Detects duplicated code, high coupling, complex conditionals, primitive obsession, long functions, and other structural issues. Produces a structured refactoring report with prioritized findings saved to docs/_refacs/. Use when auditing code quality, preparing for a refactoring sprint, or reviewing architectural health. Don't use for style/formatting issues, performance optimization, or security audits.
    2.9k repo stars
  67. ▌
    QA Report 4 · compozy bundle
    Generate comprehensive test plans, test cases, regression test suites, automation annotations, and bug reports for QA engineers. Includes Figma MCP integration for design validation. Use when planning QA before execution, documenting test strategies, marking which flows require E2E follow-up, or creating structured bug reports. Do not use for executing tests against a live repository or running verification gates — use qa-execution for that.
    2.9k repo stars
  68. ▌
    QA Execution 4 · compozy bundle
    Executes full-project QA like a real user by discovering the repository verification and E2E contracts, running build, lint, test, and startup commands, exercising core workflows end-to-end through CLI, HTTP, and browser interfaces, requiring automated regression coverage for supported critical flows, fixing root-cause regressions, and rerunning the full gate. Uses the agent-browser companion skill for Web UI validation when a web surface exists. Use when validating a branch, release candidate, migration, refactor, or risky commit. Do not use for static code review only, one-off unit test edits, planning test cases, or architecture brainstorming without execution — use qa-report for planning and documentation.
    2.9k repo stars
  69. ▌
    Releasepr 4 · compozy bundle
    Guides adoption and use of pr-release in a consuming repository: installation, GitHub Actions wiring, configuration, conventional-commit release PRs, explicit beta/stable/legacy plans, custom notes, dry-runs, publication lifecycle, and troubleshooting. Use when a project depends on compozy/releasepr. Not for editing pr-release itself or general semantic-versioning advice.
    2.9k repo stars
  70. ▌
    No Workarounds 3 · compozy bundle
    Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.
    2.9k repo stars
  71. ▌
    Bubbletea 3 · compozy bundle
    Build terminal user interfaces with Go and Bubbletea framework. Use for creating TUI apps with the Elm architecture, dual-pane layouts, accordion modes, mouse/keyboard handling, Lipgloss styling, and reusable components. Includes production-ready templates, effects library, and battle-tested layout patterns from real projects.
    2.9k repo stars
  72. ▌
    Cy Fix Reviews 3 · compozy
    Executes provider-agnostic PR review remediation using existing review round files under .compozy/tasks/<name>/reviews-NNN/. Use when resolving batched review issues, updating issue markdown files, implementing fixes, and verifying the result. Do not use for PRD task execution, review export/fetch, or generic coding tasks without review issue files.
    2.9k repo stars
  73. ▌
    Cy Workflow Memory 3 · compozy bundle
    Maintains workflow-scoped task memory for Compozy runs using .compozy/tasks/<name>/memory/ files. Use when a task prompt provides workflow memory paths and requires the agent to read, update, compact, and promote durable context across PRD task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.
    2.9k repo stars
  74. ▌
    Ship Pr 2 · compozy bundle
    Ships a finished feature, bug fix, or refactor end-to-end — explores the change's impact on docs/site/README, generates release notes (via pr-release if present, otherwise inline from git log), writes a complete PR description (including QA screenshots and summary when qa-report/qa-execution artifacts exist), commits staged changes following the repo's commitlint config, opens the PR via gh CLI, and optionally launches a CodeRabbit review watch loop. Use when a feature/bug/refactor is implementation-complete and ready to ship. Do not use for draft PRs without finished work, for amending an already-merged PR, for repo-level release publishing (use pr-release directly), or for in-progress development checkpoints.
    2.9k repo stars
  75. ▌
    QA Report 3 · compozy bundle
    Plans real-user QA deliverables: personas, journey maps, exploratory charters, persona/journey/tour/CFR test cases, regression suites, Figma validation checks, automation intent, and user-impact bug reports. Writes artifacts under <qa-output-path>/qa/ for qa-execution to consume. Use when planning QA before execution, documenting journey-driven test strategy, marking flows that need E2E follow-up, or filing structured bug reports. Do not use for live execution, AI implementation audits, CI gate ownership, or technical integration/security/performance suites; use qa-execution or agent-output-audit instead.
    2.9k repo stars
  76. ▌
    Git Rebase 3 · compozy bundle
    Intelligently handle git rebase operations and resolve merge conflicts while preserving features and maintaining code quality. Use when rebasing feature branches, resolving conflicts across commits, and ensuring clean linear history without losing changes. Don't use for merge-commit workflows, cherry-picking individual commits, or initial repository setup.
    2.9k repo stars
  77. ▌
    Testing Boss 3 · compozy bundle
    Comprehensive testing doctrine for software and AI systems — covers positive patterns, anti-patterns, gates for coding agents writing tests, CI discipline, and an LLM/agent evaluation primer. Use when authoring or reviewing tests, adding mocks, deciding test placement, generating tests via agents, debugging flaky CI, designing eval suites for LLM features, or rebuilding a brittle test suite. Contains 12 positive patterns (selector hierarchy, table-driven, builders, real-system gates), 25 anti-patterns across Brittleness, Flakiness, Mock-misuse, Process, and AI-specific families, 7 mandatory gates for agents writing tests, flaky-test taxonomy with quarantine workflow, contract / property / mutation testing patterns, and an oracle-ladder primer for LLM-as-judge and agent eval. Language-agnostic — pseudo-code only. Don't use for general code review, library-specific debugging unrelated to tests, non-testing CI pipeline design, or production observability.
    2.9k repo stars
  78. ▌
    Agent Exploration 3 · compozy bundle
    Dispatches scoped-write explorer subagents in parallel for general research and exploration of any codebase, topic, or domain. The operator passes --path (output directory), --agents (parallel count), and --prompt (research question). The parent scouts the territory first to divide work, dispatches N explorer subagents that each write one analysis file at <path>/analysis/NN_analysis_<slug>.md following a seven-section schema, then synthesizes <path>/analysis/summary.md. The skill self-contains the explorer subagent definition and prompts the operator to install it at .claude/agents/explorer.md when absent. Use when running parallel multi-area research that must produce written artifacts. Do not use for competitor-only research already covered by cy-research-competitors, single-file lookups answerable by Explore, or edits to existing code.
    2.9k repo stars
  79. ▌
    Architectural Analysis 3 · compozy bundle
    Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health. Don't use for style/formatting issues, performance profiling, security audits, or feature-level code review.
    2.9k repo stars
  80. ▌
    Skeeper 3 · compozy bundle
    Explains how to use skeeper to keep spec artifacts (SPEC.md, ADRs, RFCs, plan/PRD/TechSpec markdown, custom globs) next to the code they describe without polluting main-repo history. Covers strict hooks, the tracked skeeper.lock file, namespaces, Git-like status/pull/push/sync/restore workflows, track/untrack, repair, SKEEPER_SKIP, and the GitHub Action. Use when setting up skeeper, configuring a sidecar, syncing or checking a lockfile, recovering drift or failed syncs, auditing bypasses, or wiring CI. Do not use for general Git hook questions, repos with no .skeeper.yml and no intent to add one, or editing skeeper internals.
    2.9k repo stars
  81. ▌
    QA Execution 3 · compozy bundle
    Executes full-project QA like a real user by discovering the repository verification and E2E contracts, running build, lint, test, and startup commands, exercising core workflows end-to-end through CLI, HTTP, and browser interfaces, requiring automated regression coverage for supported critical flows, fixing root-cause regressions, and rerunning the full gate. Uses the agent-browser companion skill for Web UI validation when a web surface exists. Use when validating a branch, release candidate, migration, refactor, or risky commit. Do not use for static code review only, one-off unit test edits, planning test cases, or architecture brainstorming without execution — use qa-report for planning and documentation.
    2.9k repo stars
  82. ▌
    Cy Create Prd 2 · compozy bundle
    Creates a Product Requirements Document through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, or brainstorming requirements. Do not use for technical specifications, task breakdowns, or code implementation.
    2.9k repo stars
  83. ▌
    Cy Create Techspec 2 · compozy bundle
    Creates a Technical Specification by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, or when technical architecture decisions need documentation. Do not use for PRD creation, task breakdown, or direct code implementation.
    2.9k repo stars
  84. ▌
    Refactoring Analysis 3 · compozy bundle
    Analyzes codebases to identify refactoring opportunities based on Martin Fowler's catalog of code smells and refactoring techniques. Detects duplicated code, high coupling, complex conditionals, primitive obsession, long functions, and other structural issues. Produces a structured refactoring report with prioritized findings saved to docs/_refacs/. Use when auditing code quality, preparing for a refactoring sprint, or reviewing architectural health. Don't use for style/formatting issues, performance optimization, or security audits.
    2.9k repo stars
  85. ▌
    Compozy 3 · compozy bundle
    Explains Compozy capabilities, CLI commands, core workflow skills, optional extension skills, configuration, artifact structure, reusable agents, and extensions. Use when the user asks how to use Compozy, what commands are available, how the workflow pipeline works, or how to configure a workspace. Do not use for executing workflow steps — use the specific cy- skills instead.
    2.9k repo stars
  86. ▌
    Fumadocs 3 · compozy bundle
    Authoritative guide for the Fumadocs documentation framework — Core (headless), MDX (content loader), and UI (Tailwind v4 layouts and components). Use when scaffolding a Fumadocs project, editing source.config.ts, wiring loader() and meta.json conventions, picking a search adapter, composing DocsLayout/Notebook/Flux/Home layouts, customising the MDX component map, integrating OpenAPI specs, generating OG images, exporting PDF/EPUB/RSS, or configuring i18n across Next.js, React Router, TanStack Start, and Waku adapters. Surfaces canonical install snippets per adapter, decision tables for entry modes and content sources, and the most common pitfalls (Tailwind v3 silent failure, ESM-only config, .source/ generation, layout/page import mismatch, slug collisions, edge runtime ban). Don't use for generic MDX/Markdown questions outside Fumadocs, for unrelated React framework setup, or for projects that don't use fumadocs-core/fumadocs-mdx/fumadocs-ui.
    2.9k repo stars
  87. ▌
    Releasepr 3 · compozy bundle
    Guides adoption and day-to-day use of the pr-release CLI in a consuming GitHub repository: installing the binary, wiring the release GitHub Actions workflow, authoring .pr-release.yaml, following conventional commits for semantic versioning, adding custom release notes with add-note, validating with dry-run, and understanding the release-PR then merge then production-release lifecycle. Use when a project depends on compozy/releasepr (pr-release) and needs to configure, run, or troubleshoot its release automation. Not for editing the pr-release Go source itself, and not a general changelog or semantic-versioning tutorial.
    2.9k repo stars
  88. ▌
    Tech Logos 3 · compozy
    Install official tech brand logos from the Elements registry. Use when user needs logos for tech companies (Clerk, Vercel, GitHub, etc.), AI providers (OpenAI, Anthropic, Claude), social platforms, or any brand assets. Triggers on "logo", "brand", "icon for [company]", "add [company] logo", placeholder logo detection, or when building landing pages, auth UIs, or integrations showcases. Don't use for custom in-house logos, generic icon libraries (Lucide, Heroicons), or marketing image assets.
    2.9k repo stars
  89. ▌
    Deep Review 3 · compozy bundle
    Deep review of branch diffs, working trees, or GitHub PRs at any size. Use when the user asks for CodeRabbit-grade review, an incremental re-review after new pushes, publication of findings to a PR, a cross-LLM peer-review verdict round, or conformance review against spec artifacts. Don't use for applying fixes, reviewing specs or PRDs as documents, or quick single-file feedback.
    2.9k repo stars
  90. ▌
    Favicon Gen 3 · compozy bundle
    Generate custom favicons from logos, text, or brand colours. Produces all required formats: favicon.svg, favicon.ico, apple-touch-icon.png, icon-192/512.png, and web manifest. Use when initialising websites, replacing CMS default favicons, converting logos to favicons, creating branded icons from initials, or troubleshooting favicon not displaying, iOS black square, or missing manifest.
    2.9k repo stars
  91. ▌
    Tailwindcss 3 · compozy bundle
    Tailwind CSS v4 conventions — semantic design tokens for theme-safe styling, mobile-first responsive layouts, and v4-first utilities. Use when styling components or writing className utilities with Tailwind. Don't use for plain CSS, CSS-in-JS (styled-components, emotion), or other utility frameworks.
    2.9k repo stars
  92. ▌
    Cy Loop Tasks 3 · compozy bundle
    Task-graph execution loop for Compozy specs — self-healing checkpoint driver that ships a techspec end to end by executing its authored task graph (_tasks.md + task_NN.md), one atomic commit per Phase B task, QA, then deep-review peer-review rounds until SHIP. Use for continuous codex-loop goal runs over a .compozy/tasks/<slug> whose work is decomposed into task files, or with --frontend to delegate frontend tasks to herdr workers. Do not use for one-off tasks, PRD/TechSpec authoring, or a slug with spec documents but no task graph (use cy-implement-spec).
    2.9k repo stars
  93. ▌
    Cy Create Tasks 5 · compozy bundle
    Decomposes PRDs and TechSpecs into robust, independently implementable task files, assigning every test case from _tests.md to exactly one task and enriching tasks from codebase exploration. Use when a PRD or TechSpec exists and needs to be broken down into executable tasks, or when task files need enrichment with implementation context. Do not use for PRD creation, TechSpec generation, or direct task execution.
    2.9k repo stars
  94. ▌
    Cy Execute Task 3 · compozy bundle
    Executes one PRD task end-to-end uninterrupted — resolves spec conflicts autonomously, implements, validates, and updates tracking without pausing for questions. Use when a prompt includes a task specification that must be implemented, validated, and reflected in task tracking files. Do not use for PR review batches, generic coding tasks without a PRD task file, or standalone verification-only work.
    2.9k repo stars
  95. ▌
    Cy Final Verify 5 · compozy
    Enforces fresh verification evidence before any completion, fix, or passing claim, and before commits or PR creation. Use when an agent is about to report success, hand off work, or commit code. Do not use for early planning, brainstorming, or tasks that have not yet reached a concrete verification step.
    2.9k repo stars
  96. ▌
    Cy Review Round 3 · compozy bundle
    Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with cy-fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.
    2.9k repo stars
  97. ▌
    Cy Spec Preflight 3 · compozy bundle
    Loads the AGH spec authoring playbook plus relevant lessons, standing directives, glossary, and active context before cy-create-prd, cy-create-techspec, or cy-create-tasks runs. Applies phase-specific checks: PRDs stay business-focused, TechSpecs carry the six quality markers, and every spec/task captures extensibility integration, agent-manageability, config lifecycle, QA tail coverage, and Web/Docs Impact. Use whenever an AGH spec authoring skill is about to run. Do not use for spec execution, review remediation, or non-spec brainstorming output.
    2.9k repo stars
  98. ▌
    Storybook Stories 3 · compozy bundle
    Create, update, or refactor Storybook stories following the project's standard patterns. Use this skill when adding stories for new components, updating existing stories, or fixing Storybook-related issues.
    2.9k repo stars
  99. ▌
    Cy Web Docs Impact 3 · compozy bundle
    Audits a backend AGH change for downstream impact on web/, packages/site, agent-operable CLI/HTTP/UDS surfaces, extensibility surfaces, and config.toml. Adds explicit impact subitems to backend tasks, even when the conclusion is no impact. Use when drafting tasks or reviewing TechSpec coverage for changes touching contracts, handlers, CLI verbs, config, extensions, hooks, skills, tools, resources, bundles, registries, bridges, MCP, or agent workflows. Do not use for purely internal refactors with no public, agent, config, docs, or extensibility surface.
    2.9k repo stars
  100. ▌
    Cy Spec Peer Review 3 · compozy bundle
    Cross-LLM peer review of a TechSpec via compozy exec — scoped Markdown findings for user-directed incorporation. Use when a TechSpec draft has already been approved and the user wants an external review round, especially for autonomy/network/memory-impacting designs. Do not use for PRDs, automatic approval gates, code review batches, or auto-looped review cycles.
    2.9k repo stars