designer
01Agent
Role: Product & UX Designer for {{Project}} -- owns Service Design, Interaction Design, Visual Design, and Branding.
Agent
Role: Product & UX Designer for {{Project}} -- owns Service Design, Interaction Design, Visual Design, and Branding.
Agent
Role: Senior Developer for {{Project}} -- implements user stories with critical engineering judgment.
Agent
Role: Senior Frontend Developer for {{Project}} -- implements frontend stories with critical engineering judgment.
Agent
Role: Head of Engineering (CTO) for {{Project}} -- owns the "How" (Architecture and Feasibility).
Agent
Role: Head of Product (CPO) for {{Project}} -- owns the "What" (Scope) and "Why" (Strategy).
Agent
Role: User Experience Engineer for {{Project}} -- bridges Design and Frontend Engineering, owns design system layer, writes agent-optimized user stories for the Backlog.
Skill Claude CodeCodex
Multi-phase deep research with parallel retrieval agents. Use when the user asks for in-depth research, analysis, comparison, market intelligence, or any query that requires systematic evidence gathering from multiple sources with citations and confidence scoring. Triggers on: "deep research", "research this"…
Skill Claude CodeCodex
Write user stories optimized for AI coding agents. Use this skill when writing backlog stories that will be implemented by Developer or Frontend Developer agents. Produces structured, XML-tagged specifications with explicit context, states matrix, file paths, and escalation criteria. Based on research from SWE-bench…
Skill Claude CodeCodex
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Skill Claude CodeCodex
Create Maestro UI test flows for user stories and features.
Skill Claude CodeCodex
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes…
Hook Claude Code
Runs when a session starts, executing session-start.sh. From michele-prandina/ClaudE2E.
Hook Claude Code
Runs before the agent uses a tool for Bash tool calls, executing pre-bash.sh. From michele-prandina/ClaudE2E.
Hook Claude Code
Runs after a tool call finishes for Edit and Write tool calls, executing post-edit.sh. From michele-prandina/ClaudE2E.
Settings file Claude Code
Agent settings declaring 3 hook events (SessionStart, PreToolUse, PostToolUse).
Cursor rule Cursor
Product Designer persona — service design, interaction design, visual design, iOS HIG, branding. Use when creating wireframes, user journeys, service blueprints, or design specs.
Cursor rule Cursor
Senior Developer persona — implements backend user stories, production code, git workflow. Use when coding backend features, writing tests, or implementing API endpoints.
Cursor rule Cursor
Senior Frontend Developer persona — implements frontend user stories, UI code, manages dev server workflow. Use when building React components, implementing screens, or frontend testing.
Cursor rule Cursor
Head of Engineering persona — architecture decisions, technical feasibility, stack governance. Use when discussing tech stack, ADRs, performance, security, or system design.
Cursor rule Cursor
Head of Product persona — planning, user stories, UX decisions, scope guardian. Use when discussing product strategy, PRDs, user research, feature proposals, or backlog prioritization.
Cursor rule Cursor
UX Engineer persona — design tokens, design system components, Storybook, visual QA, writes agent-optimized user stories. Use when implementing design systems, writing stories, or managing tokens.
Cursor rule Cursor
Core project instructions — lifecycle, global rules, escalation model, code standards, safety guardrails, vault structure, documentation standards. Loaded in every session.
Cursor rule Cursor
Error logging protocol — log resolved errors to Known Errors Log for institutional memory. Inherited by all personas.
Cursor rule Cursor
Vault sync protocol — update Obsidian vault after every meaningful action. Inherited by all personas.