Skip to content

supercheck-io/supercheck / .agents/skills/feature-implementation

supercheck-feature-implementation

Verified

Implement a new or changed Supercheck feature end to end, such as adding an API route or server action, a new test, job, or monitor capability, across schema, auth/RBAC, services, routes/actions, UI, queues/workers, CLI/recorder, tests, docs, and deployment contracts.

Supercheck feature implementation

Use the domain skill matching the feature. For cross-cutting work, load each applicable domain skill; every skill is self-contained and available directly under .agents/skills.

flowchart LR
  INTENT[User intent] --> CONTRACT[Behavior and ownership contract]
  CONTRACT --> DATA[Schema and migration]
  CONTRACT --> AUTH[Auth and RBAC]
  DATA --> SERVICE[Business logic]
  AUTH --> SERVICE
  SERVICE --> API[Routes and actions]
  SERVICE --> QUEUE[Queue and worker]
  API --> UI[UI, hooks, CLI, recorder]
  QUEUE --> TEST[Test matrix]
  UI --> TEST
  TEST --> DOC[Docs and skills]

Choose the required layers

Feature shapeTypical layers
UI-onlyComponent/page, accessibility, client/server boundary, UI tests
App CRUDSchema/migration, validation, RBAC, service, route/action, hook/UI, audit, tests
App and workerApp CRUD plus shared queue contract, processor/service, capacity/cancellation, integration tests
External API/CLIBearer auth, stable schemas/status/output, rate limits, compatibility tests, docs
Recorder/browserExtension permissions/messages, app bridge/API, browser tests, store/release docs
Provider integrationCredential/webhook boundary, idempotency, durable state, failure/recovery, provider acceptance
InfrastructureConfig/manifests, secrets, security controls, rollout/rollback, rendered/live validation

Only add layers the behavior needs. Avoid speculative tables, CRUD, queues, abstractions, and client state.

Implementation workflow

  1. Define user-visible behavior, owning organization/project scope, authorization resource/action, state transitions, limits, retention, side effects, and failure behavior.
  2. Read neighboring code and tests. Reuse central helpers: auth context (app/src/lib/auth-context.ts), RBAC (app/src/lib/rbac/), validation (app/src/lib/validations/), security (app/src/lib/security/), queues (app/src/lib/queue.ts), worker utilities (worker/src/common/utils/), storage, and logging.
  3. Identify public and rolling-deployment contracts before changing schema, API, queue payload, statuses, CLI JSON, extension messages, or environment variables.
  4. Implement the smallest complete vertical slice, preserving cloud and self-hosted behavior.
  5. Add regression tests for happy, denied, malformed, cross-tenant, dependency-failure, retry/idempotency, cancellation, and cleanup paths as applicable.
  6. Update public docs, examples, environment/deployment configuration, and affected agent skills in the same change.

Data and API rules

  • Determine scope from the owning resource; authorize before reads/mutations and scope queries at the database boundary.
  • Validate all external input using existing schemas/patterns and bound strings, arrays, files, URLs, and result sizes.
  • Generate/review database migrations and handle existing data, uniqueness, indexes, deletion, and version skew.
  • Keep internal errors in structured/redacted logs and return stable safe public errors/status codes.
  • Audit security, membership, secret, billing, and administrative mutations.

Background and external side effects

  • Keep app/worker queue contracts in parity and compatible during rolling deployments.
  • Do not enqueue decrypted secrets. Resolve scoped values immediately before isolated use.
  • Make retries safe and idempotent; use durable idempotency keys/records for provider, webhook, usage, and notification effects.
  • Propagate cancellation and cleanup through every layer; release capacity/resources exactly once.
  • Use SSRF-safe fetching for user-controlled URLs and verify signatures for inbound provider events.

UI and public client rules

  • Prefer Server Components and direct React Query data; keep query keys/invalidation exact.
  • Preserve loading, empty, error, keyboard, focus, labels, and responsive states.
  • CLI JSON and exit codes, recorder messages, public APIs, and configuration formats are compatibility contracts.
  • Server-side enforcement remains authoritative for permissions, entitlements, limits, and feature modes.

Completion gate

  • Run focused then broad checks from affected package directories (commands in supercheck-testing-qa, or /check in Claude Code).
  • Verify diff cleanliness and no generated/secret files.
  • State local evidence and outstanding browser, CI, provider, deployment, billing, or production gates separately.
  • Do not claim merge/release readiness only because implementation tests pass.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall