ai-product-design-rules: Skill for Cursor

.cursor/skills/ai-product-design-prd/SKILL.md

ai-product-design-prd is a skill for Cursor from luiscielak/ai-product-design-rules. It costs 50 tokens per session (709 once invoked), scanned A, original, MIT.

A product requirements document writer. A PRD is a document that explains what a product should do, who it serves, why it matters, and how success will be measured.

In plain words
What is it for?
Use it to define product scope, success metrics, user stories, primary user journeys, assumptions, and project risks.
Why use it?
It removes ambiguity before design and implementation by turning goals, user needs, constraints, and risks into an actionable scope.

Skill for Cursor

Written for Cursor: installed under .cursor/.

This is luiscielak/ai-product-design-rules's own configuration. It tells Cursor how to work on ai-product-design-rules itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-product-design-rules configures →

Reuse

Borrowing it

Nothing to install: this file belongs to luiscielak/ai-product-design-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/luiscielak/ai-product-design-rules/main/.cursor/skills/ai-product-design-prd/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/luiscielak/ai-product-design-rules

Made for: Cursor.

Wrote 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.

agentmods badge for ai-product-design-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-prd/github.svg)](https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-prd)
Your own site
<a href="https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-prd"><img src="https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-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.

agentmods 80×15 button for ai-product-design-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/luiscielak/ai-product-design-rules/ai-product-design-prd"><img src="https://agentmods.dev/badge/skills/luiscielak/ai-product-design-rules/ai-product-design-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 709 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00709
Opus 5.5 $0.00020 $0.00284
Sonnet 5.5 $0.00010 $0.00142
Haiku 4.5 $0.00005 $0.00071

Measured 5d ago against content hash dad3d15d1ab3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ai-product-design-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 5d 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.

.cursor/skills/ai-product-design-prd/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRD (Product Owner)

Produce a concise, actionable PRD aligned to measurable success metrics.

Pipeline

Stage in the ai-product-design chain: scaffold → /prd → /lofi → /midfi → /hifi → /ui-proto.

  • Previous: scaffold (ai-product-design-new-project)
  • Next: /lofi (ai-product-design-lofi)

To run the whole chain in one pass, use the ai-product-design-workflow orchestrator.

Inputs

Required: product_name, target_users, key_problem, business_goals, success_metrics, primary_flows (list).
Also: constraints, assumptions, risks, stakeholders, timeline.

Artifact root

All deliverables for this product go under a single artifact_root:

  1. Definition: artifact_root is the directory that contains this product’s PRD.md and/or DESIGN-BRIEF.md (same folder is ideal). If files are split, prefer the folder the user attached or the one containing PRD.md.
  2. Resolve in order: (a) Parent directory of an attached or @-referenced PRD.md / DESIGN-BRIEF.md; (b) explicit path the user gives for the product docs folder; (c) greenfield only (/new-project or PRD with no path): projects/{project_name}/docs/.
  3. Do not default to repo-global docs/wireframes/, docs/ui-design/, or root docs/PRD.md when artifact_root is known.

Output

File: {artifact_root}/PRD.md — for greenfield with no path yet, use projects/{project_name}/docs/PRD.md as artifact_root.

PRD Content Structure

  1. Overview — product_name, elevator_pitch, problem_statement
  2. Goals and Non-Goals
  3. Target Users and Personas
  4. User Stories (INVEST) and Primary Flows
  5. Scope — MVP vs Post-MVP
  6. Functional Requirements — FR-001, FR-002… (each maps to a user story and metric)
  7. Non-Functional Requirements — NFR-001…
  8. Acceptance Criteria — Gherkin-style where useful
  9. Success Metrics — north star + leading indicators (target, timeframe, measurement method each)
  10. Dependencies and Constraints
  11. Assumptions and Open Questions
  12. Risks and Mitigations
  13. Release Plan and Milestones

Read the full file on GitHub · 63 lines

Changes

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.

  1. 5d ago First seen · 63 lines · 50 tokens per session scan A dad3d15d1ab3

Subscribe to this mod's changes

ai-product-design-prd is a skill published in the GitHub repository luiscielak/ai-product-design-rules (4 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 709 once invoked, about $0.0002 per session on Opus 5.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-10-28.

Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens