session-search
|
xero
|
security-audit
|
visual-testing
|
ubs-scanner
|
terraphim-hooks
|
acceptance-testing
|
1password-secrets
|
disciplined-specification
|
caddy
|
code-review
|
architecture
|
community-engagement
|
debugging
|
devops
|
disciplined-design
|
disciplined-implementation
|
disciplined-quality-evaluation
|
disciplined-research
|
home-kitchen-systems
Create, update, or audit Future Water Systems Home Kitchen Systems page content or related home kitchen water purifier messaging, including Kerala/Thrissur market context, competitor positioning, product differentiation, and educational explanations of RO/UV/UF systems.
new-page
Build new pages in this project when asked to create a new page or major page layout. Enforce design_rules.md and client/src/design-tokens.ts, include a full-blue trust-gradient section, include a Buy Now Pay Later style section, include at least two sections with placeholder images, omit the risk section, and run ESLint with eslint.config.cjs after changes.
admin-design
Minimal, high-clarity admin UI design for this repo. Use when redesigning /admin pages (translation manager, dashboards, tables, forms), defining admin design tokens, or improving admin UX/keyboard workflows without changing core functionality.
social-feed-integration
Integrate and maintain the Instagram/Facebook social wall for case studies and blogs in this repo, including manual import workflows, Meta Graph API setup, compliance endpoints, and SEO/performance/security guardrails. Use when adding social posts, updating the importer, wiring UI placement, or handling Meta tokens and data deletion callbacks.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
translation-manager
Translation Manager for this repo: Supabase-backed translations, admin UI under /admin/translation-manager with Home live preview and click-to-select translation, Edge Functions (translations-get/admin/suggest), build-time translation pipeline, and security hardening. Use when planning or editing translation manager UI, Supabase schema/migrations, translation scripts (seed/pull), Edge Functions, translation auth, or troubleshooting translation data/AI suggestions.
GSD Verifier
Validates implemented work against spec requirements with empirical evidence
GSD Planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification
Context Health Monitor
Monitors context complexity and triggers state dumps before quality degrades
GSD Debugger
Systematic debugging with persistent state and fresh context advantages
Empirical Validation
Requires proof before marking work complete — no "trust me, it works"
GSD Executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management
GSD Plan Checker
Validates plans before execution to catch issues early
GSD Codebase Mapper
Analyzes existing codebases to understand structure, patterns, and technical debt
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
receiving-code-review
Use 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
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use 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
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
noop-generator
Generate production-ready Express + TypeScript + PostgreSQL + Redis projects. Use when the user wants to create a new backend service, API, or microservice from scratch. Automatically invoked when discussing project scaffolding or generation.
noop-entity
Generate new domain entities with full CRUD infrastructure in noop-based projects. Use when adding new resources, tables, or API endpoints to an existing project.
noop-architecture
Guide for implementing code following the noop function-first, layered architecture. Use when writing handlers, services, database operations, or middleware. Automatically invoked when working on noop-based projects.
Page 1652 of 1688 · 84385 results
