hypha-web

Maintain AI proposal discovery and form preparation when adding or updating Agreements create routes. Use when adding a new proposal type, changing create form fields, or updating select-create-action / select-settings-action menus.

Scaffold an SDD ticket workspace when starting a new unit of work. Reads the developer config, classifies the task, picks the SDD level, and creates the ticket folder in hypha-context. Trigger when the developer says: 'I'm starting #X', 'let's begin <ticket>', 'new task', or 'starting work on X'. (To resume an in-progress ticket use hypha-task-resume. To wrap up use hypha-checkpoint.)

Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move

Read or update Hypha's GitHub issues, PRs, and project board (#14 "Hypha Platform — Active Work") via the gh CLI. Use when a technical developer (github.enabled in their config) says "update the board", "sync this to GitHub", "move

Draft a shareable summary of work — a daily update, a spec brief for the team, or a focused issue to run by the team. Three auto-detected modes: daily (recent work + next steps), spec (spec summary + acceptance criteria), issue (specific topic to raise). Writes to .hypha-context.local/briefs/ (local draft — developer decides what to share). Trigger when someone says: 'generate a brief', 'draft something to share', 'share my daily update', 'brief the team on this spec', 'I want to run this by the team', or 'create a brief for the team call'.

Surface an idea, observation, or proposal for team discussion without owning the improvement — creates a committed entry in the shared feedback/ folder in hypha-context. Two flavors: internal (engaged dev flagging something to discuss collectively) or external (any contributor providing input for engaged devs to act on). Trigger when someone says: 'flag this for the team', 'I have feedback on X', 'log this idea without a ticket', 'note this for discussion', 'I want to surface this but not own it'.

Draft a shareable summary of work — a daily update, a spec brief for the team, or a focused issue to run by the team. Three auto-detected modes: daily (recent work + next steps), spec (spec summary + acceptance criteria), issue (specific topic to raise). Writes to .hypha-context.local/briefs/ (local draft — developer decides what to share). Trigger when someone says: 'generate a brief', 'draft something to share', 'share my daily update', 'brief the team on this spec', 'I want to run this by the team', or 'create a brief for the team call'.

Surface an idea, observation, or proposal for team discussion without owning the improvement — creates a committed entry in the shared feedback/ folder in hypha-context. Two flavors: internal (engaged dev flagging something to discuss collectively) or external (any contributor providing input for engaged devs to act on). Trigger when someone says: 'flag this for the team', 'I have feedback on X', 'log this idea without a ticket', 'note this for discussion', 'I want to surface this but not own it'.

Record progress at a checkpoint — end of session/day, after a milestone or PR, at a phase transition. Updates ticket spec header, decisions, and activity log in hypha-context; updates the platform view; commits and pushes both repos. Trigger when the developer says: 'let's checkpoint', 'wrap up for the day', 'update the status and activity log', or 'record where we are'.

Resume an in-progress Hypha ticket in a new session. Loads ticket context from hypha-context, assesses the current SDD phase, copies the frozen spec into the satellite, and briefs what's next. Trigger when the developer says: 'I'm continuing #X', 'let's resume X', 'I'm back on this ticket', 'picking up where I left off', 'continue #X', or when starting Phase B after Phase A was completed.

Record progress at a checkpoint — end of session/day, after a milestone or PR, at a phase transition. Updates ticket spec header, decisions, and activity log in hypha-context; updates the platform view; commits and pushes both repos. Trigger when the developer says: 'let's checkpoint', 'wrap up for the day', 'update the status and activity log', or 'record where we are'.

Scaffold an SDD ticket workspace when starting a new unit of work. Reads the developer config, classifies the task, picks the SDD level, and creates the ticket folder in hypha-context. Trigger when the developer says: 'I'm starting #X', 'let's begin <ticket>', 'new task', or 'starting work on X'. (To resume an in-progress ticket use hypha-task-resume. To wrap up use hypha-checkpoint.)

Resume an in-progress Hypha ticket in a new session. Loads ticket context from hypha-context, assesses the current SDD phase, copies the frozen spec into the satellite, and briefs what's next. Trigger when the developer says: 'I'm continuing #X', 'let's resume X', 'I'm back on this ticket', 'picking up where I left off', 'continue #X', or when starting Phase B after Phase A was completed.

Run and write Playwright e2e tests for hypha-web. Handles dev server startup (with Zellij pane support), feature flag cookies, and test execution. Use when: running e2e tests, debugging test failures, writing new spec files, or asking "run tests", "e2e", "playwright", "test the chat panel", "test this feature". Also trigger when test output shows feature-flag-related failures (missing buttons, elements not found) or cookie/SSR issues. Do NOT use for unit tests, component tests, or non-Playwright testing.

Model Context Protocol (MCP) architecture, server design, Cursor integration, security, and debugging. Use when developers ask about MCP servers, tools/resources/prompts, stdio or remote transports, mcp.json, OAuth, or troubleshooting agent-to-server connectivity.

Review code for security vulnerabilities and hardening opportunities. Use when auditing code for XSS, injection, auth flaws, CSP issues, dependency risks, secrets exposure, or any security concern. Also trigger when the user says "security review", "security audit", "check for vulnerabilities", "is this secure", or mentions OWASP, CVE, or CSP.

Hypha UI stack: Tailwind CSS 4, shadcn/ui, Radix UI colors. Use when working with packages/ui, design tokens, component specs, or styling in hypha-web.

Generate and execute conventional commit messages by analyzing git diffs and conversation context. Use when creating git commits, generating commit messages, or documenting changes in conventional commit format.

Generate a new modular agent role in .agents/roles/ with references/ component reuse and documentation-first behavior. Use when creating new roles like "create a senior clerk engineer" or "create a senior neon db engineer", or migrating an existing prompt to the modular role architecture.

Designs, reviews, and optimizes GitHub Actions workflows at senior level. Use when creating or modifying .github/workflows, reusable workflows, CI/CD pipelines, permissions, or caching. Always checks https://github.com/features/actions before answering.

Maintains and performance-optimizes this Turborepo + pnpm monorepo and GitHub Actions pipelines. Use when editing turbo.json, package scripts, pnpm workspace config, or .github/workflows to reduce CI duration, cache misses, and unnecessary work.

Auto-fix CodeRabbit review comments - get CodeRabbit review comments from GitHub and fix them interactively or in batch

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

AI-powered code review using CodeRabbit. Default code-review skill. Trigger for any explicit review request AND autonomously when the agent thinks a review is needed (code/PR/quality/security).

Create and manage translations for hypha-web using next-intl. Use when translating components, adding new translation keys, adding new locales, or working with i18n in this project.