Browse reusable instructions for your AI tools. Copy and customize a prompt, or download a skill for a supported agent.
Create system design documentation templates. TRIGGERS - Use when user needs help with system-design-template related tasks.
Build team charters with agreements. TRIGGERS - Use when user needs help with team-charter-builder related tasks.
Track and prioritize technical debt for remediation. TRIGGERS - Use when user needs help with tech-debt-tracker related tasks.
Write user stories with acceptance criteria. TRIGGERS - Use when user needs help with user-story-writer related tasks.
Create value stream maps with optimization. TRIGGERS - Use when user needs help with value-stream-mapping related tasks.
Design weekly planning templates with priorities. TRIGGERS - Use when user needs help with weekly-planning related tasks.
Generate weekly status reports with progress, blockers, and next steps. TRIGGERS - Use when user wants a weekly report, status update, or progress summary.
Design internal wiki architectures. TRIGGERS - Use when user needs help with wiki-architecture related tasks.
Optimize workflows for speed, cost, and error reduction. TRIGGERS - Use when user needs help with workflow-optimizer related tasks.
Balance workloads across team members fairly. TRIGGERS - Use when user needs help with workload-balancer related tasks.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
Requirements engineering: INVEST criteria for user stories, Given-When-Then acceptance criteria with edge cases, MoSCoW prioritization, vertical slices, story mapping, decomposition patterns, non-functional requirements, Definition of Done. Use when writing user stories, breaking down epics, defi...
Systematic step-by-step reasoning with revision and branching. Use for complex problems, multi-stage analysis, design planning, problem decomposition, or encountering unclear scope, alternative approaches needed, revision requirements.
Use when writing SOPs that require precise requirement levels using RFC 2119 constraint keywords (MUST, SHOULD, MAY). Covers proper usage of requirement keywords for deterministic agent behavior.
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD w...
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript pr...
Create data fetching services with circuit breaker pattern for API resilience. Services handle fetch, cache, retry, and expose typed data to panel components.
Debug client-side issues using browser developer tools. Identify JavaScript errors, styling issues, and performance problems in the browser.
Manage application state using Redux, MobX, Zustand, and Context API. Use when centralizing state for complex applications with multiple components.
Apply appropriate design patterns (Singleton, Factory, Observer, Strategy, etc.) to solve architectural problems. Use when refactoring code architecture, implementing extensible systems, or following SOLID principles.
Try another platform, a broader search, or fewer filters.
Explore all resourcesResource formats: Prompts are ready to copy into a conversation. Skills install into the compatible agent shown on their page.
How it worksInclude the instructions, intended platforms, author, and license. Submissions are reviewed before publication.