decisions
Decisions
Overview
This skill maintains a chronological record of significant project decisions in docs/decisions.md. It captures important architectural and design decisions, especially those involving tradeoffs, to create a permanent record of why key choices were made.
When to Use This Skill
Proactive (Conservative): Suggest recording decisions only when there is a clearly significant architectural choice, such as:
- Choosing between database systems (e.g., SQLite vs PostgreSQL)
- Selecting major frameworks or libraries
- Deciding on core architectural patterns (e.g., monolith vs microservices, rendering approach)
- Making fundamental design choices that will shape the project long-term
Do NOT proactively suggest for:
- Minor implementation details
- Routine coding decisions
- Small refactoring choices
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