Skip to content
Skills Library
Design & UX · Research

reference

/reference

Use when the user provides a reference, such as another project, app, or design, to draw ideas from.

Repository
skills ↗
Licence
MIT
Last repository change
03.11.2026

Assessment and security

100/ 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.
Content35 / 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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.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 the user provides a reference, such as another project, app, or design, to draw ideas from.

Original author description

Use when the user provides a reference, such as another project, app, or design, to draw ideas from.

How it works

  1. Workflow
  2. Closed-source references
  3. Hard Boundaries
  4. Good Use Of References
Original SKILL.md headings · 62 lines, 679 words
SKILL.md preview
---
name: reference
description: Use when the user provides a reference, such as another project, app, or design, to draw ideas from.
---

# Reference

Use the provided reference as learning material for the current task. The target project remains the source of truth.

## Workflow

1. Identify the reference artifact and the target deliverable.
   - Accept local paths, repositories, source snippets, URLs, screenshots, documents, or described examples.
   - If the reference cannot be accessed and the task depends on it, ask for the missing artifact or credentials.

2. Keep downloaded references local and untracked.
   - If a reference repository, archive, website export, document bundle, or other resource must be cloned or downloaded, place it inside the target project under a gitignored scratch path such as `.refs/`.
   - Ensure the scratch path is ignored before downloading or cloning into it.
   - Do not stage, commit, or reference the downloaded path, repository name, URL, provenance, or other linking details in project code, comments, docs, tests, commit messages, or generated artifacts.
   - Use the local copy only as temporary working material for inspection.

3. Inspect only what is relevant.
   - Read enough of the reference to understand patterns, constraints, interaction design, architecture, algorithms, naming conventions, data flow, tests, or edge cases that matter to the task.
   - Prefer targeted search and representative files over broad copying or exhaustive ingestion.
   - Treat reference runtime commands as read-only unless the user explicitly asks to run or modify that project.

4. Evaluate before adopting.
   - Check whether each observed idea fits the target project's architecture, style, dependencies, licensing constraints, security posture, and user request.
   - Do not assume the reference is correct, current, maintainable, idiomatic, complete, or better than the target codebase.
   - When the reference conflicts with local conventions or requirements, prefer the target project.

5. Adapt concepts, not artifacts.
   - Recreate behavior in the target project's style using its existing helpers, abstractions, and tests.
   - Translate ideas into fresh implementation details suited to the target codebase.
   - Use established APIs, protocols, formulas, or short idiomatic snippets only when they are generic and necessary.

6. Preserve provenance silence in public artifacts.
   - Do not add comments, docstrings, documentation, commit messages, generated UI text, filenames, symbols, or variable names that identify or link to the reference.
   - Do not say "based on", "inspired by", "copied from", or equivalent provenance notes in project artifacts.
   - In user-facing summaries, describe the implemented result and validation, not the reference's identity, unless the user explicitly asks for comparison or attribution.
   - Silence covers public project artifacts only. If the project keeps private provenance records, record the reference there. Attribution that the reference's license requires goes in the project's public licensing record, which is not a provenance leak.

## Closed-source references

If the reference is closed-source or proprietary, or using it would mean
reverse engineering or extracting from a binary, installer, package, firmware,
or website, or reproducing distinctive copyrighted creative work, stop and
ask: name the situation and wait for the user's decision before reading
further. Open-source references under a license compatible with the project
need only attribution, recorded the way the project records it.

## Hard Boundaries

- Do not copy whole files, asset sets, large exact code chunks, distinctive text, branding, private data, secrets, or license headers from the reference.
- Do not vendor the reference or add it as a dependency unless the user explicitly requests that and the target project policy allows it.
- Do not preserve reference-specific names, URLs, comments, IDs, examples, mock data, or visual branding unless they are part of a public standard the target project already uses.
- Do not let local reference scratch directories appear in `git status`, staged diffs, committed paths, or committed text.
- Do not weaken local quality standards just because the reference takes a shortcut.

## Good Use Of References

- Learn the shape of a feature, workflow, state machine, API integration, UI interaction, test case, or edge-case handling.
- Compare tradeoffs, then choose the approach that best fits the target project.
- Use the reference to discover questions and risks, not to outsource judgment.
- Keep final changes independently understandable without requiring readers to know the reference exists.
Files in this package (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · yuri-xyz/skills100MIT
lucastamoios/skills100MIT
zph/dotfiles100MIT

Database snapshot: 13.11.2026 · package version f334a11c2c9f (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

No similar skills in the database.

Feedback and reports

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