with one click
dotfiles
dotfiles contains 24 collected skills from 0spura, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Define how approved requirements will be implemented (service boundaries, APIs, data model, integrations, failure modes, technical contracts) before coding.
Explore how something should work before building it (product philosophy, component design, or feature behavior) and converge on an approved design.
Empirical HCI and UX guidelines per device type to ground UI design decisions.
Pressure-test an existing plan, design, or decision, interrogating every decision point one question at a time until hidden assumptions and weak points surface.
Turn approved requirements into typed tracker work items, shaped from a template and ready for the implementation loop to dispatch.
Drive an approved backlog to done. Selects the next unblocked item and dispatches it by type to the right agent, sending feature and refactor to implement-item, bug to debug, and perf to perf.
Use after implementation is committed on a branch to open or update a PR, write the PR body, link work items, monitor checks, and handle CI feedback. Works for a feature or a standalone fix/perf/refactor.
Formalize an approved design into a versioned requirements specification (what the system must do, for whom, under which constraints) before architecture.
Record an architecture decision by creating, updating, or superseding an ADR after a significant, costly-to-reverse technical choice is approved.
Explore how something should work before building it (product philosophy, component design, or feature behavior) and converge on an approved design.
Formalize an approved design into a versioned requirements specification (what the system must do, for whom, under which constraints) before architecture.
Draft an academic paper or thesis in phases that survive peer review, from fitting the venue through shaping the contribution, storyboarding the skeleton, and writing the prose.
Pressure-test a paper at any phase, whether shape, skeleton, draft, or final, by reviewing it three ways at once, four when citations need checking against sources, then synthesize a mock notification with a phased revision list.
Build a single-file HTML slide deck in three light passes, content and mechanics first, then a unique visual identity, then the assembled deck, so revising the sequence never means regenerating the whole file.
Use after implementation is committed on a branch to open or update a PR, write the PR body, link work items, monitor checks, and handle CI feedback. Works for a feature or a standalone fix/perf/refactor.
Record an architecture decision by creating, updating, or superseding an ADR after a significant, costly-to-reverse technical choice is approved.
Define how approved requirements will be implemented (service boundaries, APIs, data model, integrations, failure modes, technical contracts) before coding.
Discipline for running a code-changing task, covering scope, spec alignment, verification, and clean handoff.
The quality bar for code, covering simplicity, clarity, tests, and secure-by-construction.
Pressure-test an existing plan, design, or decision, interrogating every decision point one question at a time until hidden assumptions and weak points surface.
Turn approved requirements into typed tracker work items, shaped from a template and ready for the implementation loop to dispatch.
Drive an approved backlog to done. Selects the next unblocked item and dispatches it by type to the right agent, sending feature and refactor to implement-item, bug to debug, and perf to perf.
Turn a recurring failure or repeated correction into a durable fix by mining the pattern, proposing one bounded edit to a rule, skill, or agent, and applying it only after approval.
Empirical HCI and UX guidelines per device type to ground UI design decisions.