compozy
- 311 skills
- 0 followers
- 5 days ago last updated
- ▌ Repository Orientation 2 · compozyMap an unfamiliar repository before changing it. Use when a task crosses packages, public contracts, persistence, runtime wiring, or verification lanes and the owning architecture is not yet clear.
- ▌ Qmd 2 · compozy bundleSearch markdown knowledge bases, notes, and documentation using QMD. Use when users ask to search notes, find documents, or look up information.
- ▌ React 2 · compozy bundleBuild React 19 components and hooks under React Compiler: state, Effects, memoization, props/refs, Actions, use(), compiler/lint setup, and Vitest tests. Excludes React Native, other frameworks, and backend-only Node.js.
- ▌ Deslop 2 · compozyReview a changed diff for accidental complexity or generated-code noise. Use when requested or when the diff shows those symptoms; an equivalent review of unchanged inputs need not repeat.
- ▌ Shadcn 2 · compozy bundleBest practices for building UI components with shadcn/ui. Use when creating, customizing, or styling components with shadcn, working with Radix UI primitives, implementing design tokens, or following compound component patterns.
- ▌ Tanstack 2 · compozy bundleTanStack Query, Router, and Form patterns for React. Use when writing useQuery/queryOptions, mutations, caching, file-based routes, search params, loaders, or TanStack Form validation. Don't use for TanStack Start, TanStack DB/collections, Zustand client state, or non-TanStack routing.
- ▌ UI Craft 2 · compozy bundleDesign, 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.
- ▌ Bubbletea 2 · compozy bundleBuild interactive Go TUIs with Bubbletea, Elm architecture, Lipgloss, layouts, and keyboard/mouse handling. Excludes plain-text CLIs, web/desktop GUIs, and other TUI frameworks.
- ▌ QA Report 2 · compozy bundleCreate or update living QA docs, journey/scenario plans, persona session charters, and the durable bug registry. qa-execution owns live sessions, browser evidence, and fix loops.
- ▌ To Prompt 2 · compozy bundleTurn code, issues, or context into a handoff brief for another LLM — relevant context and preserved user decisions, written to docs/prompts/. Use when packaging a bug fix, an improvement, or a feature request for an external LLM to implement. Don't use for simple one-shot questions or end-user-facing copy.
- ▌ Turborepo 2 · compozy bundleTurborepo 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.
- ▌ QA Execution 2 · compozy bundleRun persona-driven dogfooding through public product interfaces using living QA docs. Use for release candidates, branch diffs, migrations, and user-facing changes. qa-report owns planning; CI and specialist test suites are outside this workflow.
- ▌ Testing Boss 2 · compozy bundleAuthor or review software tests and LLM/agent evals; choose test placement and mocks, diagnose flaky CI, or repair brittle suites. Excludes unrelated code review, debugging, CI design, and production observability.
- ▌ Xstate Store 2 · compozy bundleBuild, test, integrate, or migrate XState Store v4: transitions, effects, schemas, selectors, atoms, extensions, React bindings, and fromStore. Excludes XState state-machine design, other stores, and Query server state.
- ▌ Golang Master 2 · compozy bundleWrite or review production Go: errors, concurrency, context, types, generics, safety, tests, benchmarks, profiling, modernization, and module structure. Project/framework conventions and third-party API lookup have separate owners.
- ▌ No Workarounds 2 · compozy bundleEvaluate a proposed fix that suppresses errors, diagnostics, or symptoms. Use for suspected workarounds and unavoidable external defects; not as a mandatory stage for every bug fix.
- ▌ Compozy 2 · compozy bundleOperate CompozyOS. Use when working with CompozyOS sessions, agents, native tools, skills, memory, Network, tasks, Loops, Goals, Terminal, desktops and windows, bridges, automation, extensions, or configuration. Don't use for unrelated projects.
- ▌ Skeeper 2 · compozy bundleSet up or operate skeeper sidecar specs, hooks, locks, namespaces, sync, recovery, bypass audits, and CI. Excludes skeeper internals, general Git hooks, and repos with no skeeper setup intent.
- ▌ Fumadocs 2 · compozy bundleSet up, customize, or troubleshoot Fumadocs Core/MDX/UI: adapters, loaders, navigation/layouts, search, MDX components, OpenAPI, OG images, exports, and i18n. Excludes generic Markdown, unrelated framework setup, and non-Fumadocs projects.
- ▌ Better UI 2 · compozy bundleBuild or review UI components and visual details, including animation, hover/focus states, shadows, borders, icons, alignment, and micro-interactions. Use for interface polish or visual details that feel off.
- ▌ Humanizer 2 · compozy bundleEdit or review text to remove AI-writing patterns and make it sound natural. Covers inflated claims, vague attribution, repetitive structures, vocabulary, punctuation, and transitions.
- ▌ Releasepr 2 · compozy bundleAdopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
- ▌ SEO Audit 2 · compozy bundleAudit or diagnose site SEO, rankings/traffic losses, crawl/indexing issues, metadata, page speed, and Core Web Vitals, including general requests for SEO help. Programmatic pages, schema markup, and AI search have separate workflows.
- ▌ Demo Video 2 · compozy bundleAgent-recorded product demo videos — choreograph a real browser flow with a cursor overlay and camera zooms, encode from raw frames, and package for PR evidence or social posts. Project specifics come from .demo-video.yaml.
- ▌ Impeccable 2 · compozy bundleDesign, redesign, review, or improve frontend interfaces and design systems. Covers UX, visual hierarchy, accessibility, responsive behavior, performance, copy, theming, motion, edge cases, browser iteration, and ambitious effects. Excludes non-UI work.
- ▌ Tech Logos 2 · compozyReuse 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.
- ▌ Copywriting 2 · compozy bundleWrite or improve marketing page copy, headlines, and CTAs for home, landing, pricing, feature, about, or product pages. Email sequences and popup copy have separate workflows.
- ▌ Deep Review 2 · compozy bundleReview branch diffs, working trees, or PRs in depth, including incremental, CodeRabbit-grade, cross-LLM, and spec-conformance reviews or requested publication of findings. Excludes fixes, spec-document reviews, and quick single-file feedback.
- ▌ Favicon Gen 2 · compozy bundleGenerate website favicons from logos, initials, or brand colors, including SVG/ICO, Apple touch icons, app icons, and a manifest. Use for site setup, replacements, or broken favicon troubleshooting.
- ▌ Tailwindcss 2 · compozy bundleTailwind 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.
- ▌ Skill Doctor 2 · compozy bundleEvaluate agent instructions and skills using local conversation outcomes, cost, and concrete failures. Use for a requested history-based audit or revalidation; not as a mandatory completion step.
- ▌ Better Colors 2 · compozy bundleUse OKLCH for web colors: conversion, palettes, contrast, gamut, semantic tokens, Tailwind v4 theming, and light/dark or increased-contrast appearances.
- ▌ Better Layout 2 · compozy bundleStructure or review page/component layouts: grouping, spacing, alignment, hierarchy, disclosure, responsive/container breakpoints, safe areas, full bleed, and RTL/logical properties.
- ▌ Cy Loop Tasks 2 · compozy bundleRun a requested Compozy spec delivery loop through task checkpoints, scoped QA, review, and PR CI.
- ▌ Use Modern Go 2 · compozy bundleUse the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
- ▌ Eng Design 2 · compozyCompozy 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.
- ▌ Lesson Learned 2 · compozy bundleExtract evidence-backed engineering lessons from recent changes or incidents. Use for requested reflection, lesson updates, or retiring an obsolete workflow rule.
- ▌ Cy Create Tasks 3 · compozy bundleCreate or refine a task graph from an existing Compozy spec, with outcome, dependency, and test ownership.
- ▌ Cy Final Verify 3 · compozy bundleAssess a spec task or delivery claim against its contract and available verification evidence.
- ▌ Cy Issue To Spec 2 · compozy bundlePublishes 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.
- ▌ Mermaid Diagrams 2 · compozy bundleCreate Mermaid diagrams for software architecture, data models, code, processes, and user flows. Use for diagramming, visualization, flow explanations, and class, sequence, ER, C4, state, Git, chart, or timeline representations.
- ▌ Better Typography 2 · compozy bundleChoose, configure, style, or review web typography: fonts, OpenType, type scales, hierarchy, spacing, wrapping/truncation, decoration, text controls, accessibility, and punctuation.
- ▌ Cy Spec Preflight 2 · compozy bundleCheck a Compozy spec or task artifact during authoring or when its contracts change.
- ▌ Storybook Stories 2 · compozy bundleCreate, update, refactor, or troubleshoot Storybook stories using project conventions. Excludes component implementation, token changes, E2E browser tests, and other documentation.
- ▌ Cy Web Docs Impact 2 · compozy bundleAudit backend tasks/spec coverage for Web, site, public agent interfaces, config, and extensibility impact. Use for contract, handler, CLI, extension/hook/tool/registry/bridge/MCP/workflow changes; excludes refactors without those impacts.
- ▌ Cy Spec Peer Review 2 · compozy bundleRun a requested external review of an approved Compozy spec; continue follow-ups in the same reviewer session and incorporate only user-selected findings. Excludes product drafts, automatic gates, code reviews, and review loops.
- ▌ Herdr Orchestration 2 · compozy bundleOrchestrate Claude and Codex worker TUIs from a controller agent — one worker per named herdr tab, driven over the herdr socket CLI.
- ▌ App Renderer Systems 2 · compozy bundleCreate, extend, or debug frontend domain modules organized under systems/. Covers adapters, Query hooks, local state, and public exports; excludes generic components and backend implementation.
- ▌ Better Accessibility 2 · compozy bundleBuild or review accessible UI components, dialogs, menus, forms, and custom widgets. Covers semantics/ARIA, keyboard/focus, screen readers, contrast, motion, and touch targets; use for reported accessibility issues.
- ▌ Eng QA Bootstrap 2 · compozy bundleBootstraps 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.
- ▌ Systematic Debugging 2 · compozy bundleInvestigate a failure with an unclear cause, repeated unsuccessful fixes, or a cross-component boundary. Use existing reproduction evidence for a localized bug; not a mandatory multi-stage ritual for every edit.
- ▌ Cy Tasks Tail QA Pair 2 · compozy bundleAdd or repair the final QA planning/execution pair in a requested cy-loop-tasks graph.
- ▌ Eng UI Screenshot 2 · compozy bundleScreenshot capture for deterministic PNG evidence and visual-contract bundles for Compozy Storybook stories and local UI URLs. Use for visual audits, regression diffs, and design-parity checks. Do not use for interactive E2E flows, remote authenticated sites, or Storybook test execution.
- ▌ Eng Code Guidelines 2 · compozy bundleGo 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, cleanup, or network skill when those domains apply.
- ▌ Eng Data Boundaries 2 · compozy bundleData-boundary audit for Compozy route loaders, TanStack Query caches, paginated catalogs, filters, ordering, totals, live streams, workspace-scoped reads, and their backend APIs. Use when adding, changing, or debugging those paths. Don't use for presentational-only UI or backend work with no public read-model impact.
- ▌ Eng Real Scenario QA 2 · compozy bundleDogfoods 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.
- ▌ Eng Schema Migration 2 · compozy bundleChange Compozy SQLite tables, columns, indexes, constraints, triggers, or seed data under internal/store or internal/memory using append-only Goose migrations and owning generators. Excludes in-memory structures, Markdown memory, and non-SQLite caches.
- ▌ Eng Test Conventions 2 · compozy bundleGo 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.
- ▌ Eng Worktree Isolation 2 · compozy bundleIsolates 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.
- ▌ Cy Fix Reviews 2 · compozyExecutes agent-authored review remediation using existing 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 task execution, review generation, or generic coding tasks without review issue files.
- ▌ Eng Cleanup Failure Paths 2 · compozy bundlePartial-failure cleanup audit for Compozy Go functions. Use when a changed function acquires, registers, starts, claims, leases, or opens more than one fallible resource before returning. Do not use for pure transformations, read-only helpers, or test-only code.
- ▌ Cy Create Tasks 4 · compozy bundleCreate or refine a task graph from an existing CompozyOS spec, with outcome, dependency, and test ownership.
- ▌ Cy Execute Task 2 · compozy bundleImplement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
- ▌ Cy Final Verify 4 · compozy bundleAssess a spec task or delivery claim against its contract and available verification evidence.
- ▌ Cy Review Round 2 · compozy bundlePerforms a comprehensive code review of a spec implementation and generates a review round directory with issue files compatible with cy-fix-reviews. Use when reviewing implemented spec 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 spec tasks, or editing source code.
- ▌ Eng Consolidate Test Suites 2 · compozy bundleUse when adding, moving, reviewing, or auditing tests in Compozy to identify the invariant, owning layer, and canonical suite before changing coverage. Do not use as a replacement for framework-specific testing skills or final verification gates.
- ▌ Eng Contract Codegen Coship 2 · compozy bundleContract 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.
- ▌ Cy Workflow Memory 2 · compozy bundleMaintains workflow-scoped task memory for CompozyOS 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 spec task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.
- ▌ Cy Orchestrate Tasks 2 · compozyConducts one spec's tasks by delegation — spawns a dedicated bounded worker session per task, dispatches the briefing, and uses the task file on disk for completion state and checks its verification evidence. Use when a prompt names a spec slug under .compozy/tasks/ and asks for its tasks to be orchestrated across worker sessions. Do not use for implementing a task directly, for review remediation, or for QA and pull-request work.
- ▌ Batuta Routing 2 · compozyDefault cost/complexity routing table for the batuta conductor. Read at bootstrap as a starting point, validated against the live provider catalog, then stored as the per-workspace loop configuration; the stored workspace override is authoritative afterwards.
- ▌ Zod · compozy bundleZod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).
- ▌ AI Sdk · compozy bundleAnswer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, or tools, (2) Want to build AI agents, chatbots, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, etc.), streaming, tool calling, or structured output.
- ▌ React Doctor · compozyUse when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.
- ▌ Deslop · compozyReview a changed diff for accidental complexity or generated-code noise. Use when requested or when the diff shows those symptoms; an equivalent review of unchanged inputs need not repeat.
- ▌ Turborepo · compozy bundleTurborepo 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.
- ▌ Xstate Store · compozy bundleBuild, test, integrate, or migrate XState Store v4: transitions, effects, schemas, selectors, atoms, extensions, React bindings, and fromStore. Excludes XState state-machine design, other stores, and Query server state.
- ▌ Golang Master · compozy bundleWrite or review production Go: errors, concurrency, context, types, generics, safety, tests, benchmarks, profiling, modernization, and module structure. Project/framework conventions and third-party API lookup have separate owners.
- ▌ Writing Agents Md · compozyCreate, audit, shorten, or scope AGENTS.md and CLAUDE.md instructions. Use writing-skills for on-demand skills; excludes human-facing documentation and READMEs.
- ▌ Testing Anti Patterns · compozyUse when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
- ▌ Receiving Code Review · compozyUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- ▌ Verification Before Completion · compozyUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- ▌ Golang Pro · compozy bundleImplements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
- ▌ Brainstorming · compozyYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- ▌ Skill Best Practices · compozy bundleAuthors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
- ▌ Humanizer · compozy bundleEdit or review text to remove AI-writing patterns and make it sound natural. Covers inflated claims, vague attribution, repetitive structures, vocabulary, punctuation, and transitions.
- ▌ SEO Audit · compozy bundleAudit or diagnose site SEO, rankings/traffic losses, crawl/indexing issues, metadata, page speed, and Core Web Vitals, including general requests for SEO help. Programmatic pages, schema markup, and AI search have separate workflows.
- ▌ Mermaid Diagrams · compozy bundleCreate Mermaid diagrams for software architecture, data models, code, processes, and user flows. Use for diagramming, visualization, flow explanations, and class, sequence, ER, C4, state, Git, chart, or timeline representations.
- ▌ Cy Create Tasks 2 · compozy bundleCreate or refine a task graph from an existing CompozyOS spec, with outcome, dependency, and test ownership.
- ▌ Cy Final Verify 2 · compozy bundleAssess a spec task or delivery claim against its contract and available verification evidence.
- ▌ Skill Load Tips · compozyDiagnoses and refactors existing SKILL.md files whose references or assets are ignored by agents. Applies Required Reading Routers, hard STOP directives, gist-tripwire trimming, and flat one-level reference structures so bundled context is loaded deliberately. Use when auditing or rewriting long skills that feel shallow despite deep reference files. Do not use for authoring new skills from scratch, non-skill Markdown, or documentation without SKILL.md front matter.
- ▌ Sourcebot · compozySearch external libraries and frameworks using Sourcebot MCP. Use when researching external code patterns, library APIs, framework examples, or documentation from repositories like Effect-TS/effect, vercel/ai, tanstack/query. NEVER use for local project code.
- ▌ Find Rules · compozyDiscover and understand project rules, coding standards, and architectural guidelines before starting a task. Use when you need to know the constraints, patterns, or compliance requirements for a feature, file, or technology.
- ▌ Creating Spec · compozyCreate comprehensive technical specs for SDK gaps, feature modules, or system centralization efforts. Use when writing specs, PRDs, gap analysis documents, or planning centralization of scattered functionality into a single module. Triggers on "create spec", "write spec", "gap spec", "centralize", "fill the gap".
- ▌ Deep Research · compozyPerform comprehensive research and analysis using multiple discovery and analysis tools to provide a solid foundation for complex tasks.
- ▌ Rust Coding Guidelines · compozy bundleUse when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
- ▌ Dispatching Parallel Agents · compozyUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- ▌ Context7 · compozyRetrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology. Use this skill whenever answering technical questions or writing code that interacts with external technologies. This includes libraries, frameworks, programming languages, SDKs, APIs, CLI tools, cloud services, infrastructure tools, and developer platforms. Common scenarios: - looking up API endpoints, classes, functions, or method parameters - checking configuration options or CLI commands - answering "how do I" technical questions - generating code that uses a specific library or service - debugging issues related to frameworks, SDKs, or APIs - retrieving setup instructions, examples, or migration guides - verifying version-specific behavior or breaking changes Prefer this skill whenever documentation accuracy matters or when model knowledge may be outdated.
- ▌ Cc Loop · compozyInstall or refresh the CC Loop runtime for structured [[CC_LOOP ...]] activation with min="...", rounds="...", or goal="...". Use only for cc-loop setup, status, uninstall, or activation guidance.
- ▌ Exa Web Search Free · compozy bundleFree AI search via Exa MCP. Web search for news/info, code search for docs/examples from GitHub/StackOverflow, company research for business intel. No API key needed.
- ▌ No Workarounds · compozy bundleEnforce 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.