compozy
- 141 skills
- 0 followers
- 10 hours ago last updated
- ▌ Deep Review · 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 · 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 · 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 · 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 · compozy bundleUse OKLCH for web colors: conversion, palettes, contrast, gamut, semantic tokens, Tailwind v4 theming, and light/dark or increased-contrast appearances.
- ▌ Better Layout · 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 · compozy bundleRun a requested Compozy spec delivery loop through task checkpoints, scoped QA, review, and PR CI.
- ▌ Use Modern Go · compozy bundleUse the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
- ▌ Cy Create Spec · compozy bundleCreate or update a requested CompozyOS spec and its applicable companion contracts, reusing current decisions and research. Not a prerequisite for ordinary coding tasks.
- ▌ Eng Design · 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 · 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 · compozy bundleCreate or refine a task graph from an existing Compozy spec, with outcome, dependency, and test ownership.
- ▌ Cy Final Verify · compozy bundleAssess a spec task or delivery claim against its contract and available verification evidence.
- ▌ Cy Issue To Spec · 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.
- ▌ Better Typography · 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 · compozy bundleCheck a Compozy spec or task artifact during authoring or when its contracts change.
- ▌ Storybook Stories · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · compozy bundleAdd or repair the final QA planning/execution pair in a requested cy-loop-tasks graph.
- ▌ Eng UI Screenshot · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 · 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 Execute Task · compozy bundleImplement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
- ▌ Cy Review Round · 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 · 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 · 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 · 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 · 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 · 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.