design-doc
Design Doc
This skill is for when you're asked to write a design document or design specification, especially after a brainstorm or feature design session.
Design docs go into the docs/ directory in the project root. Create the folder if it doesn't exist.
The design doc is in Markdown. Choose a concise, relevant name yourself.
Content
- Be concise.
- Don't include too many code examples, unless necessary because they contain valuable details uncovered during the brainstorm or design session.
More from maragudk/skills
datastar
Guide for building interactive web UIs with Datastar and gomponents-datastar. Use this skill when adding frontend interactivity to Go web applications with Datastar attributes.
75marimo
Guide for creating and working with marimo notebooks, the reactive Python notebook that stores as pure .py files. This skill should be used when creating, editing, running, or deploying marimo notebooks.
51brainstorm
Guide for how to brainstorm an idea and turn it into a fully formed design.
41code-review
Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.
38bluesky
Guide for posting content to the Bluesky social network using the bsky terminal app. This skill should be used proactively when working in public repositories and there is interesting, shareable content (new features, insights, achievements, or announcements worth sharing with the community). Use it when asked to post to Bluesky, or when content seems worth sharing publicly.
37go
Guide for how to develop Go apps and modules/libraries. Always use this skill when reading or writing Go code.
37