Index of every page on this site: llms.txt
All skills
masihmoafi avatar

/reference-driven-product

@c0a5d13
by Masih Moafimasihmoafi/skills10 stars
Run it yourself

Use when improving or rebuilding a product from a reference app, screenshots, user feedback, or open-source alternatives, when speed and a restart guide matter. Not for isolated bug fixes or purely visual imitation.

  • 1 file
  • 2.3 KB
  • Updated 3 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/masihmoafi/skills/reference-driven-product

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈60 tokens for metadata: the name and description. ≈514 when used: this file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈242 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Improve a product from a working reference

Deliver the user's important workflows, prove each claim, and leave a guide that reaches the same place without this conversation.

  1. Destination. Read the real project state and the user's newest priorities before extending an old plan. Name the few jobs they want done and what they value in the reference; not every visible reference feature is a requirement. One acceptance contract, per the spec skill.
  2. Compare like with like. View every screenshot and use the reference. Compare the same task in the same state, and record differences in behavior, hierarchy, type, spacing and interaction. Match zoom, scale, window size and theme before measuring pixels. Check what reached the built executable, not only the source.
  3. Learn from open source. Study a few relevant projects from primary sources: version, license, platform, gaps. Separate their claims from what you observe. Read the code behind an advantage and reuse it when the architecture and license fit, with attribution. Do not switch stacks because another product looks fast.
  4. Measure fairly. Use the experiment workflow: equal work, same host, run serially; keep startup, indexing, input-to-frame and save latency apart; check correctness (exact saved text, Unicode) with speed.
  5. Fix the most valuable gap. A small change tied to the user's priority, with a check that fails today, made through the shared component or path, verified on the built artifact in the real flow. Show it early; fold feedback into the contract. Never call partial work finished or ship controls that do nothing.
  6. Guide for a restart. One project guide, linked from the orientation file, answering: what we build and what waits; which references and observations matter; the simplest architecture and why; the build-and-verify order from a clean checkout; what failed and the decision that avoids it; what is verified, unknown and next. A route, not a diary; link the evidence.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at c0a5d13. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 weeks ago

README badge

README badge for masihmoafi/skills/reference-driven-product