RepoPilot

pbakaus / impeccable

Search pbakaus/impeccable

GitHub

Code

How pbakaus/impeccable is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Declared command entry
  4. Likely start-up file
  5. Suggested starting pointAI
  6. Suggested starting pointAI
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new design detection rule

  • Define the anti-pattern rule in the detection engine with its fingerprint logic.
  • Add component styling/DOM pattern matching using font fingerprinting or DOM inspection.
  • Register the rule as an approved component or forbidden pattern in component verbs.
  • Document the rule in the skill reference or extend SKILL.src.md with new command guidance.

Add a new AI agent or integration

  • Create agent definition file following the pattern in cursor-plugin/agents/.
  • Define the agent's skills by linking to the bundled skill or creating platform-specific hooks.
  • Update AGENTS.md with agent behavior, context, and expected outputs.

Add a new design command or skill feature

  • Add the command definition and behavior to skill/SKILL.src.md with syntax and examples.
  • Implement command logic in the appropriate crate (core, detect, comp, or skills).
  • Create a reference document in skill/reference/ describing command parameters and output.
  • Update the skill manifest to include new command in platform-specific distributions.

Extend browser component detection

  • Add DOM inspection or accessibility rules to the content script.
  • Implement the detection adapter logic to translate DOM patterns to design rules.
  • Update the DevTools panel UI to display the new detection results.
  • Compile the detection logic to WASM and bundle into the extension asset.

Trace command behavior

  • Declared by package.json (bin.impeccable). Follow its exports or calls to find the implementation.

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

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

  • Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

  • Branch points393 per file on average
  • Code issues0 errors, 405 warnings
  • Largest file12,043 lines
  • Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions4 workflows
  • Tests2,390 test filesRust test · 4.8 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: crates/browser/tests

Hotspots

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