skills.rest
AndrejKiri
AndrejKiriCOMMUNITY
Explore all skills by this author →
GitHub

design-system-extraction-code-wrapup

Document post-session friction points, root causes, and fixes for design system extraction.

1|Updated Mar 30, 2026
Search Tags:#feedback#documentation#schema#tooling#post-session
One-click install
npx skills add https://github.com/AndrejKiri/prometheus-design-system --skill design-system-extraction-code-wrapup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-system-extraction-code-wrapup
Source: https://github.com/AndrejKiri/prometheus-design-system/tree/main/.claude/skills/design-system-extraction-code-wrapup
Command: npx skills add https://github.com/AndrejKiri/prometheus-design-system --skill design-system-extraction-code-wrapup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a detailed post-session analysis documenting friction points, schema confusions, and tooling gaps encountered during a design system extraction process, aiding continuous improvement.

Core Features & Use Cases

  • Friction Points Documentation: Records issues and root causes faced during a design system extraction session.
  • Fix Proposals: Suggests targeted updates to SKILL.md, schemas, scripts, or tooling to improve the process.
  • Analysis Output: Generates structured feedback reports with severity ratings and recommended directory structures for future implementation.

Quick Start

Run this Skill after completing a design-system-extraction-code session to generate a detailed feedback document for process refinement.

Frequently Asked Questions about design-system-extraction-code-wrapup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document friction points after a design system extraction session?▼

To document friction points after a design system extraction session, generate a structured feedback report summarizing root causes, severity ratings, and fixes for SKILL.md clarity, scripts, and schemas.

What is the best way to analyze schema confusions and tooling gaps in design system extraction?▼

Analyzing schema confusions and tooling gaps requires running a post-session wrap-up to record extraction issues and propose targeted updates to schemas and tooling for continuous improvement.

Can I generate directory structure recommendations alongside post-session feedback reports?▼

Yes, you can generate structured directory recommendations alongside feedback reports, ensuring actionable insights for future design system implementation are documented in Markdown.

Does this post-session analysis suggest fixes for SKILL.md and scripts?▼

Yes, the post-session analysis suggests targeted fixes for SKILL.md, scripts, schemas, and tooling by documenting root causes and proposing updates to refine the extraction process.

When do I need to run a wrap-up analysis for design system extraction?▼

You need to run a wrap-up analysis immediately after completing a design-system-extraction-code session to document friction points and generate actionable Markdown feedback for process refinement.

Related Skills

Explore More Software Engineering Skills→
kirvinkirvin

post-mortem

Analyze completed work sessions to identify friction points and propose actionable improvements.

Community
Intermediate
HuuBarHuuBar

skill-creator

Draft, validate, and iteratively improve AI skills with SKILL.md evaluations.

Community
Advanced
RebornQRebornQ
52

trellis-break-loop

Generate reusable specifications from root-cause analysis after bug fixes.

Community
Advanced
kenmulfordkenmulford

lessons-learned

Create a lessons-learned register DOCX from retrospective notes.

Community
Advanced