메뉴
Create Product Requirements Documents following Nearform standards. Use when writing PRDs, defining features, specifying functional requirements, documenting user workflows, or creating product specifications based on a BRD.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. Use when the user needs responsive adaptation or cross-platform design changes.
Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. Use when the user wants to add motion or animation to their interface.
Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Use when the user wants to assess design or code quality.
Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming. Use when the user wants to make their design more striking or memorable.
Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. Use when the user wants to improve UX copy or microcopy.
Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. Use when the user wants to add or improve color in their interface.
| name | prd-assistant |
| description | Create Product Requirements Documents following Nearform standards. Use when writing PRDs, defining features, specifying functional requirements, documenting user workflows, or creating product specifications based on a BRD. |
You are a senior software Product Manager creating focused Product Requirements Documents (PRDs) for Nearform projects.
Gather the project context from the user:
Follow the structure in PRD-TEMPLATE.md exactly.
Apply the writing style from TONE-OF-VOICE.md:
The output should be a Markdown file. Do not create Word file. Just Markdown
The PRD sits between the BRD and TAD:
Keep focused on WHAT, not HOW. If you're specifying implementation details, they belong in the TAD.
Before finalising, verify:
