AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Component

skill-maximepodgorski-claude-plugin-component · by Maximepodgorski

|

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

Install

$ agentstack add skill-maximepodgorski-claude-plugin-component

✓ 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-maximepodgorski-claude-plugin-component)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo 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 Component? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Component

Design system component workflow. Figma to production, DS-compliant.

Agent Capabilities

| Capability | Used For | Required | Fallback | |------------|----------|----------|----------| | File read/write | Specs, docs, audit reports | Yes | — | | Code search (grep/glob) | Token scan, pattern discovery, codebase conventions | Yes | — | | Shell/command execution | Quality gates (lint, typecheck) | Recommended | List commands for user to run | | Task/todo tracking | Ship loop progress | Recommended | Track in spec Progress section | | User interaction | Token creation approval, stuck escalation | Yes | — | | Figma MCP | Design context extraction (code, screenshot, hints) | Recommended | User provides spec manually |

Fallback rule: If Figma MCP is unavailable, the skill works from text input and codebase analysis. Warn the user and proceed.

Actions

| Action | Input | Output | Reference | |--------|-------|--------|-----------| | spec {name} [figma-link] | Component name + optional Figma link | Spec in ds/specs/active/ | [spec.md](references/actions/spec.md) | | doc {path\|name} | File path or component name | doc.md co-located in component folder | [doc.md](references/actions/doc.md) | | dev {name} [figma-link] | Component name + optional Figma link | Implemented component (ship loop) | [dev.md](references/actions/dev.md) | | review {path\|figma-link} | File path or Figma link | DS compliance report | [review.md](references/actions/review.md) | | spec-review {spec-path\|name} | Spec path or component name | Multi-perspective spec review | [spec-review.md](references/actions/spec-review.md) | | audit {path\|figma-link} | Directory path or Figma link | Report in ds/audits/active/ | [audit.md](references/actions/audit.md) |

Flow

Recommended (new component):
  spec → spec-review → doc → dev → review

Quick (simple component):
  dev {name} [figma-link]

Maintenance (existing component):
  review {path}    or    doc {path}

Spec validation:
  spec-review {spec-path}

System-wide:
  audit {directory}    or    audit {figma-link}

Each action is standalone — usable independently without requiring prior actions.

Philosophy

  • Figma-first: Figma is the primary input. Design context drives structure, API, and implementation.
  • Principles over opinions: Grounded in Atomic Design, BEM, DTCG, WCAG — not arbitrary preferences.
  • Reuse > create: Scan existing tokens, variables, typography BEFORE generating. Never invent.
  • Human-in-the-loop: Never create a new token without user approval.
  • Zero hardcoded values: Every hex, px, hardcoded spacing/color/radius is a CRITICAL violation.
  • Adapt to project: Read CLAUDE.md + codebase. Match the project's naming, not the skill's.
  • Stack-agnostic: Works with React, Vue, Svelte, Angular, Web Components — no hardcoded framework.

Figma Integration

When a Figma link is provided, the skill calls get_design_context from Figma MCP:

Figma link provided?
  │
  ├─ YES → Call get_design_context(fileKey, nodeId)
  │         → Receives: code + screenshot + contextual hints
  │         → Extract: component hierarchy, props, variants, tokens used
  │         → Cross-reference with codebase conventions
  │         → Proceed with enriched context
  │
  └─ NO  → Proceed from codebase / manual input only

Combined failure state:
  Figma MCP unavailable AND no component in codebase AND no spec in ds/specs/active/?
    → Error: "No context available. Provide a Figma link with MCP configured,
       create the component first, or run /component spec {name} with a description."

URL parsing:

  • figma.com/design/:fileKey/:fileName?node-id=:nodeId → convert - to : in nodeId
  • figma.com/design/:fileKey/branch/:branchKey/:fileName → use branchKey as fileKey

Token Scan Protocol

Before any dev or review action, scan the project for existing design tokens:

1. SCAN sources (in order):
   - CSS custom properties (--*)
   - SCSS/LESS variables ($*, @*)
   - Tailwind config (tailwind.config.*)
   - CSS-in-JS theme objects
   - Design token files (tokens.json, *.tokens.*)

2. DETECT naming pattern:
   - Prefix convention (--color-*, --bg-*, $spacing-*)
   - Tier structure (primitive → semantic → component)
   - Categorization (color, spacing, typography, radius, shadow)

3. MATCH Figma values to existing tokens:
   - Color: match hex/rgba to nearest token
   - Spacing: match px values to spacing scale
   - Typography: match font-size/weight/family to type tokens
   - Radius: match border-radius to radius tokens

4. FLAG missing tokens:
   - Value needed but no token exists → ASK user
   - Present options: closest match, create new, custom
   - NEVER create a token without user approval

Action Router

User input
  │
  ├─ "spec", "spec component",
  │  "component spec"                   → Load references/actions/spec.md
  │
  ├─ "doc", "document component",
  │  "component doc"                    → Load references/actions/doc.md
  │
  ├─ "dev", "develop component",
  │  "implement component",
  │  "component dev"                    → Load references/actions/dev.md
  │
  ├─ "review", "review component",
  │  "component review",
  │  "check component"                  → Load references/actions/review.md
  │
  ├─ "spec-review", "spec-review component",
  │  "component spec-review",
  │  "review spec"                      → Load references/actions/spec-review.md
  │
  └─ "audit", "audit component",
     "component audit",
     "audit ds", "audit design system"  → Load references/actions/audit.md

Loading rule: Read the action file BEFORE executing. The action file contains all logic, principles references, and templates needed.

Input detection:

Input contains figma.com URL?
  YES → Extract fileKey + nodeId, call Figma MCP
  NO  → Check if input is a file path (contains / or .)
    YES → Load from codebase
    NO  → Treat as component name, search codebase

Project Structure (in user's project)

ds/
├── specs/
│   ├── active/       ← Current specs (from spec action)
│   ├── shipped/      ← Components delivered
│   └── dropped/      ← Abandoned specs
└── audits/
    ├── active/       ← Current audit findings
    ├── shipped/      ← Fixes applied
    └── dropped/      ← Won't fix

ComponentName/
├── ComponentName.{ext}  (detected from project)
├── doc.md             ← Generated by doc action
├── ComponentName.test.ts
└── index.ts

Principles

Standards that inform every action. Loaded by review and audit for compliance checks.

| Principle | Standard | Reference | |-----------|----------|-----------| | Composition | Atomic Design (Brad Frost) | [composition.md](references/principles/composition.md) | | Naming | BEM (Block Element Modifier) | [naming.md](references/principles/naming.md) | | Tokens | DTCG (W3C Design Token Community Group) | [tokens.md](references/principles/tokens.md) | | Props API | Component API patterns | [props-api.md](references/principles/props-api.md) | | Accessibility | WCAG 2.1 AA | [accessibility.md](references/principles/accessibility.md) |

Templates

File Templates (generated output files)

| Template | Used by | Reference | |----------|---------|-----------| | Component spec | spec | [spec.md](references/templates/spec.md) | | Component doc | doc | [doc.md](references/templates/doc.md) | | Audit report | audit | [audit-report.md](references/templates/audit-report.md) |

Output Templates (chat status messages)

| Template | Used by | Reference | |----------|---------|-----------| | Spec output | spec | [spec-output.md](references/templates/spec-output.md) | | Spec-review output | spec-review | [spec-review-output.md](references/templates/spec-review-output.md) | | Doc output | doc | [doc-output.md](references/templates/doc-output.md) | | Dev output | dev | [dev-output.md](references/templates/dev-output.md) | | Review output | review | [review-output.md](references/templates/review-output.md) | | Audit output | audit | [audit-output.md](references/templates/audit-output.md) |

Configuration

All behavior is configurable by editing the skill files directly.

| What to change | Edit | |----------------|------| | Action logic | references/actions/{action}.md | | DS principles | references/principles/{principle}.md | | Output templates | references/templates/{template}.md |

References

Actions:

  • [Spec](references/actions/spec.md) | [Doc](references/actions/doc.md) | [Dev](references/actions/dev.md) | [Review](references/actions/review.md) | [Spec-Review](references/actions/spec-review.md) | [Audit](references/actions/audit.md)

Principles:

  • [Composition](references/principles/composition.md) | [Naming](references/principles/naming.md) | [Tokens](references/principles/tokens.md) | [Props API](references/principles/props-api.md) | [Accessibility](references/principles/accessibility.md)

Templates (files):

  • [Spec](references/templates/spec.md) | [Doc](references/templates/doc.md) | [Audit Report](references/templates/audit-report.md)

Output (chat):

  • [Spec](references/templates/spec-output.md) | [Doc](references/templates/doc-output.md) | [Dev](references/templates/dev-output.md) | [Review](references/templates/review-output.md) | [Spec-Review](references/templates/spec-review-output.md) | [Audit](references/templates/audit-output.md)

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.