RepoPilot

leonxlnx / taste-skill

Search leonxlnx/taste-skill

GitHub

Code

How leonxlnx/taste-skill is laid out, and where to start for common changes.

A
Architecture grade
score 100/100
0
Import cycles
lower is better
14
Files mapped
6 imports between them
100%
Layering
of imports point one way

From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.

Module map

Shade by
Entry points and orchestratorsFoundationskills12 files · 37 commitstests0 files · 5 commits

2 modules, 1 links. A link means one module imports another; thicker lines mean more imports. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.

skills121037Foundation
tests0015Entry or leaf

Where to start reading

  1. Repository root
  2. Suggested starting pointAI
  3. Suggested starting pointAI
  4. Suggested starting pointAI
  5. Suggested starting pointAI
  6. Suggested starting pointAI

Find files for a task

AI

Add a New Design Reference Category

  • Update SKILL.md to expose the new reference as an available capability
  • Add validation rules in scripts/lib/rules.mjs to lint against the new design category

Add a New Browser Verification Check

  • Implement inspection logic in scripts/lib/probe.mjs to query DOM for the design property
  • Add corresponding CSS selectors or JS queries in assets/base.js to expose data for verification
  • Create test case in evals/evals.json with expected output for the new check
  • Run lint.mjs to validate the check integrates with the rule engine

Extend the Reference Image Library

  • Add new reference image metadata to skills/taste-skill/library/photos.json or library/sites.json
  • Update related markdown reference (e.g., references/imagery.md) with context and use cases
  • Store reference assets and update scripts/assets.mjs if new asset processing is needed

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • No public API or start-up file could be picked out from the file names.

Code quality and hotspots

Largest source files

  • Branch points139 per file on average
  • Code issues0 errors, 53 warnings
  • Largest file618 lines
  • Hotspot load0 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions1 workflow
  • Tests2 test files0.17 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: tests

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.