
from dotClaude576
Run a structured discovery interview to produce a design brief that defines UX/UI direction, layout, states, and content requirements before implementation.
This skill guides a structured discovery interview and synthesises the answers into a formal design brief for a feature. It enforces preparation steps, asks targeted questions about purpose, users, content, constraints and anti-goals, and then produces a compact brief covering feature summary, primary user action, layout strategy, states, interaction model, content needs, references, and open questions. The output is handoff-ready for designers or implementation skills.
Use this skill at the start of a product or feature design cycle whenever you need clarity before engineering begins — for new features, major redesigns, or when stakeholders are misaligned. It is ideal for product managers, designers, or PM+designer pairs who want a repeatable protocol to capture requirements and reduce rework.
Design-focused workflow agents and assistant models that run conversations and create structured documents (Claude, Copilot-style assistants, or developer-focused LLMs) will be able to follow and execute this skill effectively.
A writing-shaping skill that guides an AI agent through a structured discovery loop to turn raw material into a finished article, paragraph by paragraph. No scripts included — purely instructional SKILL.md. The methodology is thoughtful (grounding concepts, format arguments, conversational pushback) but the skill lacks architectural separation, references, or output contracts.
Source URL in DB is stale (404). Actual skill content found at superdev/skills/in-progress/writing-shape/SKILL.md. The skill name in frontmatter is 'writing-shape' but DB slug is 'fradser-shape'. The skill is well-written for its niche but lacks the architectural structure expected by the skill spec (no references/, no scripts/, no clear output contracts). Marked as 'in-progress' in the repo itself.
STORM Article Polishing
Finalizes STORM-generated articles by adding summaries, removing duplicate content, and ensuring citation integrity.
STORM Engine
Core methodology engine for STORM-based research and article generation.
Claude Code Plugin Best Practices
Architectural guidance and validation for Claude Code plugins, ensuring compliance with structure, manifest, and token budget standards.