AgentStack
SKILL verified Apache-2.0 Self-run

Impeccable

skill-boraoztunc-skills-impeccable · by boraoztunc

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, ac…

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-boraoztunc-skills-impeccable

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README — it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-boraoztunc-skills-impeccable)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Impeccable? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.

Setup

Before any design work or file edits:

  1. Load context (PRODUCT.md / DESIGN.md) via the loader script.
  2. Identify the register and load the matching register reference (brand.md or product.md).
  3. If the user invoked a sub-command (e.g. craft, shape, audit), load its reference file too. This is non-negotiable: craft without craft.md loaded means you'll skip the shape-and-confirm step the user expects.

Skipping these produces generic output that ignores the project.

1. Context gathering

Two files, case-insensitive. The loader looks at the project root by default and falls back to .agents/context/ and docs/ if the root is clean. Override with IMPECCABLE_CONTEXT_DIR=path/to/dir (absolute or relative to cwd).

  • PRODUCT.md: required. Users, brand, tone, anti-references, strategic principles.
  • DESIGN.md: optional, strongly recommended. Colors, typography, elevation, components.

Load both in one call:

node {{scripts_path}}/load-context.mjs

Consume the full JSON output. Never pipe through head, tail, grep, or jq. The output's contextDir field tells you where the files were resolved from.

If the output is already in this session's conversation history, don't re-run. Exceptions requiring a fresh load: you just ran {{command_prefix}}impeccable teach or {{command_prefix}}impeccable document (they rewrite the files), or the user manually edited one.

{{command_prefix}}impeccable live already warms context via live.mjs. If you've run live.mjs, don't also run load-context.mjs this session.

If PRODUCT.md is missing, empty, or placeholder ([TODO] markers, and unpin `, detailed below.

Routing rules

  1. No argument: render the table above as the user-facing command menu, grouped by category. Ask what they'd like to do.
  2. First word matches a command: load its reference file and follow its instructions. Everything after the command name is the target.
  3. First word doesn't match: general design invocation. Apply the setup steps, shared design laws, and the loaded register reference, using the full argument as context.

Setup (context gathering, register) is already loaded by then; sub-commands don't re-invoke {{command_prefix}}impeccable.

If the first word is craft, setup still runs first, but [reference/craft.md](reference/craft.md) owns the rest of the flow. If setup invokes teach as a blocker, finish teach, refresh context, then resume the original command and target.

Pin / Unpin

Pin creates a standalone shortcut so {{command_prefix}} invokes {{command_prefix}}impeccable directly. Unpin removes it. The script writes to every harness directory present in the project.

node {{scripts_path}}/pin.mjs  

Valid `` is any command from the table above. Report the script's result concisely. Confirm the new shortcut on success, relay stderr verbatim on error.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.