prd-creator
PRD Creation Assistant
Transform software ideas into comprehensive PRDs and actionable implementation tasks through a two-part process.
Overview
This skill helps beginner-level developers.
- Receive an implementation description from the user
- Create detailed PRD documents through structured questioning
- Verify implementation prerequisites, including access, MCPs, docs, env variables, and test users
- Generate implementation task lists in JSON format for developers
- Write an overall description of the project. An executive summary that gives a high level overview of the app and its main features.
Part 1: Implementation Description
You will receive a lacking implementation description from the user. The main goal is to comprehend the intent and think about the larger architecture and a robust way to implement it, filling in the gaps.
More from pageai-pro/ralph-loop
vitest-best-practices
Comprehensive vitest testing patterns covering test structure, AAA pattern, parameterized tests, assertions, mocking, test doubles, error handling, async testing, and performance optimization. Use when writing, reviewing, or refactoring vitest tests, or when user mentions vitest, testing, TDD, test coverage, mocking, assertions, or test files (*.test.ts, *.spec.ts).
32e2e-tester
>
31frontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
24component-refactoring
Refactor high-complexity React components in frontend. Use when the user asks for code splitting, hook extraction, or complexity reduction, or when you come across a component that is too complex to understand and refactor it.
24frontend-testing
Generate Vitest + React Testing Library tests for frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
23skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
22