product-context
Skill16 starsChanged 5 months agoMITView on GitHub
Build or refresh a compact, evidence-backed product context before marketing, positioning, SEO, analytics, sales-enablement, or launch work. Use when an agent needs to understand the product, audience, proof, conversion goal, terminology, and claim boundaries without inventing commercial facts.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- jiayuewangjavy/product-designer-skills-ostheir own version, first seen Oct 28, 2026
- Ekos-Labs/skillstheir own version, first seen Oct 17, 2026
- samueljansem/skillstheir own version, first seen Oct 15, 2026
- The-AI-Thinker/product-feedback-skilltheir own version, first seen Oct 15, 2026
- designedbythanh/ai-skills-library-product-designtheir own version, first seen Oct 1, 2026
- vimulatus/skillstheir own version, first seen Sep 17, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Ekos-Labs/skills★ 8same name
- jiayuewangjavy/product-designer-skills-os★ 4same name
- designedbythanh/ai-skills-library-product-design★ 2same name
- almax000/claude-skills★ 1same name
- vimulatus/skills★ 1same name
- samueljansem/skills★ 0same name
- The-AI-Thinker/product-feedback-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository94 other files it gives its agents.
- agent-friction-ledgerSkill
- agent-learning-layer-triageSkill
- agent-operations-contractSkill
- agents-best-practicesSkill
- agent-tool-contract-reviewSkill
- anti-slop-reviewSkill
- architecture-deepening-reviewSkill
- assumption-excavationSkill
- authorized-security-routerSkill
- book-to-skillSkill
- bounded-evaluationSkill
- bounded-growth-loopSkill
- bounded-orchestration-contractSkill
- brief-first-executionSkill
- browser-verificationSkill
- bug-evidence-protocolSkill
- codex-review-loopSkill
- compaction-survivalSkill
- complexity-optimizerSkill
- confidence-fragility-reviewSkill
- context-degradation-reviewSkill
- corporate-surfaceSkill
- delivery-baseline-auditSkill
- delivery-preflight-gateSkill
- design-critique-polishSkill
- designmd-brand-kitSkill
- design-register-bootstrapSkill
- diagnoseSkill
- doc-grounded-grillingSkill
- doc-to-lora-evaluatorSkill
- durable-context-maintenanceSkill
- dynamic-workflow-packetsSkill
- editorial-surfaceSkill
- evidence-ledger-researchSkill
- filesystem-context-disciplineSkill
- fluid-interaction-reviewSkill
- frontend-product-builderSkill
- frontend-taste-layerSkill
- git-native-context-contractSkill
- goal-loop-designerSkill
- graph-guided-code-readingSkill
- handoffSkill
- happy-handoffSkill
- html-brief-artifactSkill
- html-diagram-artifactSkill
- hypothesis-diversificationSkill
- idea-to-ship-gatesSkill
- knowledge-base-enrichmentSkill
- lean-context-layoutSkill
- local-inference-tuningSkill
- loop-hardening-contractSkill
- loopops-protocolSkill
- loop-readiness-reviewSkill
- lottie-motion-builderSkill
- minimal-diff-builderSkill
- motion-review-gateSkill
- overengineering-reviewSkill
- personal-workspace-routerSkill
- phase-spec-executionSkill
- pipeline-readiness-gateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Create a small, durable context artifact that lets later product work start from evidence instead of generic positioning.
- Distinctive: line 22
Read existing product docs, public copy, analytics contracts, and relevant implementation surfaces.
- Distinctive: line 25
Keep only: product and audience, jobs and conversion action, terminology, proof and known limits, approved voice, prohibited claims, source …
- Distinctive: line 26
Ask for confirmation where positioning, ICP, pricing, competitor claims, or proof cannot be established from the repo.
- Distinctive: line 31
Never invent customer quotes, metrics, market position, availability, pricing, partner status, or legal/compliance claims.
- Distinctive: line 32
Keep personal data and private sales evidence out of a committed context file.
- Distinctive: line 33
Treat a product context as a reviewable input, not a source of truth over code, current policy, or human direction.
- Very specific: line 38
Use these headings where applicable: Product, Audience and jobs, Conversion action, Proof and limits, Language, Claim boundaries, Source …
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Context
Create a small, durable context artifact that lets later product work start from evidence instead of generic positioning.
Use When
- entering marketing, content, SEO, analytics, sales, or launch work in a repo;
- the product, audience, conversion action, or proof boundary is unclear;
- existing public copy and internal product behavior have drifted.
Workflow
- Read existing product docs, public copy, analytics contracts, and relevant implementation surfaces.
- Separate confirmed facts from assumptions, placeholders, and claims needing owner confirmation.
- Draft or update
docs/product-context.mdunless the repo already defines a better canonical path. - Keep only: product and audience, jobs and conversion action, terminology, proof and known limits, approved voice, prohibited claims, source surfaces, and last-reviewed date.
- Ask for confirmation where positioning, ICP, pricing, competitor claims, or proof cannot be established from the repo.
- Link future work to the context; do not treat it as permission to publish, spend, contact people, or change product behavior.
Guardrails
- Never invent customer quotes, metrics, market position, availability, pricing, partner status, or legal/compliance claims.
- Keep personal data and private sales evidence out of a committed context file.
- Treat a product context as a reviewable input, not a source of truth over code, current policy, or human direction.
- Preserve domain-specific safety language such as financial, booking, or approval boundaries.
Output Shape
Use these headings where applicable: Product, Audience and jobs, Conversion action, Proof and limits, Language, Claim boundaries, Source surfaces, Maintenance.
Pair With
evidence-ledger-researchfor external facts;social-publishing-gatebefore distribution;bounded-growth-loopbefore recurring optimization;loop-readiness-reviewbefore scheduling any loop.
Provenance
Adapted from the shared-context architecture in coreyhaines31/marketingskills, narrowed to evidence-backed, product-neutral context with explicit claim boundaries.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

