test
Write tests for code using test-driven development principles
technical-planning
Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.
structural-design-principles
Use when designing modules and components requiring Composition Over Inheritance, Law of Demeter, Tell Don't Ask, and Encapsulation principles that transcend programming paradigms.
solid-principles
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
rails-action-controller-patterns
Use when action Controller patterns including routing, filters, strong parameters, and REST conventions.
rails-active-record-patterns
Use when active Record patterns including models, associations, queries, validations, and callbacks.
rails-hotwire
Use when hotwire (Turbo and Stimulus) for building modern reactive Rails applications without complex JavaScript frameworks.
simplicity-principles
Use when designing solutions, adding features, or refactoring by applying KISS, YAGNI, and Principle of Least Astonishment to write simple, predictable code.
figma-sync-design-system
Sync design system components between Figma and code using Code Connect mappings
figma-generate-component
Generate production-ready code from a Figma component or frame using the Figma MCP server
review
Multi-agent code review with confidence-based filtering
refactoring
Use when restructuring code to improve quality without changing external behavior. Emphasizes safety through tests and incremental changes.
refactor
Restructure code to improve quality without changing behavior
figma-analyze-frame
Analyze a Figma frame's structure, properties, and implementation considerations
validate
Validate checklist items for a ClickUp task without changing status
proof-of-work
Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.
task
Get detailed information about a specific ClickUp task
start
Start work on a ClickUp task (transition to In Progress)
project-memory
Use when setting up or organizing Claude Code project memory (CLAUDE.md, .claude/rules/) for better context awareness, consistent behavior, and project-specific instructions.
professional-honesty
Use when responding to questions or providing information requiring professional honesty and directness over excessive agreeableness.
plan
Create tactical implementation plan for a feature or task
performance-optimization
Use when optimizing code for performance, reducing bundle size, improving load times, or fixing performance bottlenecks. Emphasizes measurement-driven optimization.
orthogonality-principle
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
search
Search for ClickUp tasks
optimize
Optimize code for performance, readability, or efficiency
legacy-code-safety
Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.
react-native-web-core
Use when working with React Native Web projects. Provides core concepts, components, and cross-platform patterns for building web applications with React Native.
react-native-web-navigation
Use when implementing navigation in React Native Web projects. Provides patterns for React Navigation, deep linking, and web-specific routing.
react-native-web-performance
Use when optimizing React Native Web performance. Provides patterns for code splitting, bundle optimization, memoization, and web-specific performance improvements.
fix
Debug and fix bugs, errors, or unexpected behavior
comment
Add a comment to a ClickUp task
update-sop
Update an existing SOP to reflect changes in tools, processes, or best practices
explainer
Use when explaining code, technical concepts, or implementation decisions. Provides structured approach to creating clear, understandable explanations tailored to the audience.
sop-structure
Use when structuring Standard Operating Procedures with proper sections, organization, and markdown formatting. Covers SOP anatomy and section organization.
monorepo-workflows
Use when setting up CI/CD, implementing versioning, optimizing workflows, or managing releases with monorepo development workflows including version management, publishing, and team collaboration practices.
monorepo-tooling
Use when setting up monorepo tooling, optimizing builds, or migrating between tools with Turborepo, Nx, Bazel, Lerna for efficient task running, caching, and code generation.
monorepo-architecture
Use when designing monorepo structure, organizing packages, or migrating to monorepo architecture with architectural patterns for managing dependencies and scalable workspace configurations.
git-storytelling-commit-messages
Use when writing commit messages that clearly communicate changes and tell the story of development. Helps create informative, well-structured commit messages that serve as documentation.
explain
Explain code, concepts, or technical decisions in clear, understandable terms
git-storytelling-branch-strategy
Use when planning git branching strategies or managing branches for development. Helps create clear development narratives through effective branch organization and workflow patterns.
git-storytelling-commit-strategy
Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.
bdd-scenarios
Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.
react-native-web-styling
Use when styling React Native Web components. Provides patterns for StyleSheet API, platform-specific styles, responsive design, and theming.
bdd-principles
Core BDD concepts, philosophy, and the Three Amigos practice
bdd-patterns
Use when applying Behavior-Driven Development patterns including Given-When-Then structure, feature files, and acceptance criteria. Use when writing BDD-style tests and specifications.
bdd-collaboration
Use when facilitating BDD collaboration between developers, testers, and business stakeholders. Use when running discovery workshops and example mapping sessions.
atomic-design-templates
Use when creating page layouts without real content. Templates define the skeletal structure of pages using organisms, molecules, and atoms.
atomic-design-quarks
Use when working with design tokens, CSS custom properties, and primitive values that form the foundation below atoms. Quarks are the sub-atomic building blocks.
atomic-design-organisms
Use when building complex organisms from molecules and atoms like headers, footers, product cards, and sidebars. Organisms are distinct UI sections.
documentation
Use when creating or updating documentation including READMEs, API docs, inline comments, or technical guides. Focuses on clarity and usefulness for the intended audience.
Page 547 of 1485 · 74219 results
