agentleFS
OlliTapioOlliTapio/claude_skills/skills/analytics-view/SKILL.md

analytics-view

Skill0 starsChanged 17 days agoMITView on GitHub

Build an analytics view (dashboard page, KPI tile, report) where the same number must agree across every surface. Use when adding charts, counters, tables, or aggregate metrics.

The file

Files
SKILL.md

analytics-view

Rules

  1. One definition, upstream. Define each metric once at the data layer — view, function, dbt model, or shared service. Downstream code reads it; never re-derives it.
  2. Fixtures mirror prod shape. Seed NULLs, edge values, unknown enum-like strings, and every column the production writer touches — not just what this view reads.
  3. Parity test across surfaces. Same metric in two places (tile vs. table, chart vs. export, API vs. UI) → one test that asserts they agree.
  4. Verify numbers before UI. Query the source directly against known fixtures. Confirm the number. Then wire the view.

When a parity test fails

Find which surface drifted (query the canonical definition), fix that surface. Don't relax the test.

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.