Skip to content
Skills Library
Management & product · Building & coding

reference-driven-product

/reference-driven-product

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.

Repository
skills ↗
Licence
MIT
Last repository change
08.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

SKILL.md has no level-two headings · 12 lines, 317 words

SKILL.md preview
---
name: reference-driven-product
description: 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.
---

# 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](../spec/SKILL.md) 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](../experiment-workflow/SKILL.md): 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.

Versions

The database has no other skills named reference-driven-product.

Database snapshot: 13.11.2026 · package version 54df2c877f22 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100reference-hunt
    Port the semantics of a reference implementation by reading its actual source, not screenshots or docs. Use when the user says "reference hunt", "照着这个实现", "像这个一样", "要做成像 X 那样", "抄作业" while pointing at a concrete product, library, or code, says "find me a reference…
  • 100competitive-analysis
    When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.