Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add rungchan2/frontend-skills --skill prdgit clone --depth 1 https://github.com/rungchan2/frontend-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rungchan2/frontend-skills/prd)<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/prd"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/prd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/prd"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00079 | $0.01241 |
| Opus 5 | $0.00039 | $0.00620 |
| Sonnet 5 | $0.00016 | $0.00248 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Generator
서비스의 핵심 가치와 요구사항을 정의하는 PRD 문서 생성 가이드.
워크플로우
1. 인터뷰 → 2. 레퍼런스 활용 → 3. 문서 생성 → 4. 검토/보완
레퍼런스 파일
| 파일 | 용도 | 언제 참조 |
|---|---|---|
references/kpi-templates.md |
도메인별 KPI 템플릿 | 성공 지표 정의 시 |
references/persona-templates.md |
직업/행동 패턴별 페르소나 | 타겟 사용자 정의 시 |
references/prioritization-frameworks.md |
RICE, MoSCoW 등 우선순위 프레임워크 | 기능 우선순위 결정 시 |
인터뷰 질문
순차적으로 질문하여 정보 수집. 한 번에 2-3개씩 질문.
필수 질문
서비스 기본 정보
- "이 서비스를 한 문장으로 설명한다면?"
- "서비스 도메인은? (예: 교육, 이커머스, 헬스케어, SaaS, 소셜, 핀테크)"
문제 정의
- "해결하려는 핵심 문제 3가지는?"
- "기존 솔루션이 부족한 이유는?"
타겟 사용자
- "주요 사용자는? (연령대, 직업, 특성)"
- "사용자의 목표와 불만은?"
핵심 가치
- "경쟁 서비스와 차별점은?"
- "성공을 어떻게 측정할 건가요?"
핵심 기능
- "반드시 있어야 하는 기능 3-5개는?"
- "각 기능의 우선순위는? (P0/P1/P2)"
선택 질문 (필요시)
- "비기능 요구사항은? (성능, 보안, 접근성)"
- "제약사항은? (예산, 일정, 인원, 기술적 제약)"
PRD 템플릿
# PRD: [서비스명]
## 1. 서비스 개요
- **서비스명**:
- **태그라인**: (20자 이내)
- **서비스 소개**: (100-200자)
- **도메인**:
## 2. 문제 정의
### 사용자 Pain Points
1.
2.
3.
### 기존 솔루션의 한계
### 해결 시 기대 가치
## 3. 타겟 사용자
### Primary Persona
- **이름**:
- **나이**:
- **직업**:
- **소득**:
- **기기 사용**: 모바일 __%, 데스크톱 __%
- **목표 (Goals)**:
-
-
-
- **불만 (Frustrations)**:
-
-
-
### Secondary Persona (선택)
- **이름**:
- **설명**:
## 4. 핵심 가치 제안
### Value Proposition
> (한 문장으로 핵심 혜택)
### 차별화 포인트
1.
2.
3.
### 성공 지표
| 지표명 | 설명 | 목표 수치 | 측정 방법 |
|--------|------|----------|----------|
| | | | |
## 5. 핵심 기능
| 기능명 | 설명 | 사용자 스토리 | 우선순위 | RICE/ICE |
|--------|------|--------------|----------|----------|
| | | "사용자로서 나는 ~를 원한다" | P0/P1/P2 | |
## 6. 비기능 요구사항
### 성능
-
### 보안
-
### 접근성
-
## 7. 제약사항
- **예산**:
- **출시 목표일**:
- **개발 인원**:
- **기술적 제약**:
- **법적/규제 요구사항**:
사용 예시
사용자: "PRD 만들어줘"
Claude: PRD를 작성하겠습니다. 먼저 몇 가지 질문을 드릴게요.
1. 이 서비스를 한 문장으로 설명한다면 뭐라고 하시겠어요?
2. 서비스 도메인은 무엇인가요? (예: 교육, 이커머스, 헬스케어, SaaS)
사용자: "AI 기반 영어 회화 연습 앱이야. 교육 도메인."
Claude: 좋습니다. 교육 도메인의 KPI 템플릿을 참고하여 성공 지표를 제안드릴게요.
이어서 질문드립니다.
1. 해결하려는 핵심 문제 3가지는 무엇인가요?
2. 기존 영어 학습 앱들이 부족한 점은 무엇인가요?
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 175 lines · 79 tokens per session scan A 53a4055966d8
prd is a skill published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,241 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…