agentleFS
vscarpentervscarpenter/gsd-task-manager/.claude/skills/inkwell-retrofit/SKILL.md

inkwell-retrofit

Skill41 starsChanged 42 days agoMITView on GitHub

Apply the Inkwell design system to an existing page or component without creating a competing styling system. Use for styling retrofits, standalone HTML explainers, docs pages, or Tailwind v4 token alignment.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when an existing page, component, or standalone document needs to adopt Inkwell while preserving its content and behavior.

    line 9
  2. Distinctive:

    Remove duplicate token declarations or competing CSS shims.

    line 15
  3. Distinctive:

    Do not use this skill to redesign the product information architecture or rewrite content.

    line 18
  4. Distinctive:

    Do not hardcode hex colors outside token definitions.

    line 32
  5. Very specific:

    Prefer semantic tokens such as --ivory, --paper, --slate, --accent, --border, and --backdrop.

    line 33
  6. Distinctive:

    Keep one saturated accent unless the page truly needs data-viz hues.

    line 34
  7. Very specific:

    Use Inkwell primitives where available: .card, .alert, .tbl, .tldr, .toc, .sec-head, .eyebrow, .badge, .chip-dot.

    line 35
  8. Distinctive:

    Keep typography roles consistent: serif for major headings and editorial callouts, mono for labels/file refs/code, sans for normal body UI.

    line 37
  9. Distinctive:

    Remove competing token systems only when Inkwell fully replaces them.

    line 44
  10. Distinctive:

    Keep app-specific extensions small, named, and layered after Inkwell imports.

    line 46
  11. Distinctive:

    Verify light and dark modes.

    line 49
  12. Distinctive:

    Verify the page renders standalone if it was standalone before.

    line 50
  13. Distinctive:

    Run the smallest meaningful set:

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

inkwell-retrofit

Use this skill when an existing page, component, or standalone document needs to adopt Inkwell while preserving its content and behavior.

Good fits

  • Re-skin an existing page with Inkwell tokens and primitives.
  • Convert a standalone HTML explainer or report to the Inkwell visual system.
  • Remove duplicate token declarations or competing CSS shims.
  • Align a Tailwind v4 project with Inkwell's token and theme model.

Do not use this skill to redesign the product information architecture or rewrite content. The default move is visual alignment, not content invention.

First read

Before editing, read:

  1. CLAUDE.md for project-specific styling rules.
  2. Existing Inkwell files under app/css/ and public/css/.
  3. Any sibling page already using Inkwell, such as a report or explainer.
  4. The target page/component end to end so content stays intact.

Core rules

  • Reuse existing Inkwell tokens before adding project-specific tokens.
  • Do not hardcode hex colors outside token definitions.
  • Prefer semantic tokens such as --ivory, --paper, --slate, --accent, --border, and --backdrop.
  • Keep one saturated accent unless the page truly needs data-viz hues.
  • Use Inkwell primitives where available: .card, .alert, .tbl, .tldr, .toc, .sec-head, .eyebrow, .badge, .chip-dot.
  • Preserve the 1.5px hairline convention unless the project explicitly documents a different value.
  • Keep typography roles consistent: serif for major headings and editorial callouts, mono for labels/file refs/code, sans for normal body UI.
  • Preserve dark-mode behavior through data-theme and tokens, not per-component ad hoc overrides.
  • SVG fills and strokes should reference tokens so diagrams theme correctly.

Retrofit steps

  1. Identify the current styling source: global CSS, inline styles, Tailwind utilities, standalone <style>, or linked CSS.
  2. Remove competing token systems only when Inkwell fully replaces them.
  3. Map existing colors, borders, typography, spacing, and callouts to Inkwell tokens and primitives.
  4. Keep app-specific extensions small, named, and layered after Inkwell imports.
  5. Replace hardcoded rgba/hex values with semantic tokens.
  6. Preserve content and IDs unless the task explicitly asks for content edits.
  7. Verify light and dark modes.
  8. Verify the page renders standalone if it was standalone before.

Tailwind v4 integration checklist

  • Inkwell imports are reachable through the app CSS pipeline.
  • @import statements appear before other rules.
  • @theme aliases are defined once.
  • [data-theme] dark-mode cascade works.
  • Old v3 config token duplication is removed only after equivalent v4 tokens exist.
  • External consumers still have any needed files under public/css/.

Verification

Run the smallest meaningful set:

  • bun typecheck
  • bun lint
  • bun run build
  • targeted tests for touched components, if any
  • browser smoke test for light, dark, and responsive behavior

PR notes

In the PR body, include:

  • What visual system changed.
  • What content intentionally stayed unchanged.
  • Any intentional deviation from default Inkwell guidance.
  • Light/dark verification notes.
  • A short list of hardcoded style values removed.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.