Singular · overview
Storage
How singularskills organizes artifacts in the project directory across all domains.
Directory Structure
singularskills stores all artifacts under a .singularskills/ directory in your project root, with one subdirectory per workflow folder (a domain workflow uses its domain's name), plus the run log:
.singularskills/
log.jsonl ← run log: one JSON line per run, approval and skipped gate
design/<component>/ ← 01- through 05- phase files
research/<topic>/ ← 01- through 04- phase files
marketing/<topic>/ ← 00- through 04- phase files + utilities
branding/<brand>/ ← 01- through 05- phase files + assets/
legal/<topic>/ ← 00- through 04- phase files + utilities
coaching/<subject>/ ← Review files (no numbered phases)
leadership/<team>/ ← 01- through 05- phase files + day-to-day tools
accessibility/<target>/ ← 01- through 05- phase files
development/<feature>/ ← 01- through 04- phase files
project-management/<project>/ ← 00- through 04- phase files + utilitiesFile Naming Convention
Phase artifacts use a numbered prefix pattern to maintain order:
| Prefix | Purpose |
|---|---|
00- | Foundation/setup phase (Strategy, Initiate, Assess) |
01- | First active phase (Empathize, Discover, Reach, Plan) |
02- | Second phase (Define, Evaluate, Act, Build, Sprint) |
03- | Third phase (Ideate, Design, Report, Convert, Review, Test, Comply) |
04- | Fourth phase (Prototype, Deliver, Engage, Remediate, Improve, Govern, Develop) |
05- | Fifth phase (Test, Guidelines, Retest, Sustain) |
Non-phase files (utilities, reviews, day-to-day tools) use descriptive names without numbered prefixes.
Phase artifacts open with a frontmatter block and end with ## Decisions and ## Open questions. A bypassed gate (--skip-checks) is recorded as a skipped line in .singularskills/log.jsonl. The Workflows page describes both formats. Commit the .singularskills/ folder with your project.
Organizing by Subject
Within each domain directory, artifacts are grouped by subject — the second-level directory name:
- Design: component name (e.g.,
button,modal,data-table) - Research: research topic (e.g.,
onboarding-friction,pricing-model) - Marketing: campaign or product topic
- Branding: brand name
- Project Management: project name
- Legal: legal matter or contract type
- Coaching: review subject
- Leadership: team name
- Accessibility: audit target (page, component, or flow)
- Development: feature name
Accessing Artifacts
To read artifacts from any domain, use the standard path pattern:
.singularskills/<domain>/<subject>/<file>.mdAll artifacts are plain Markdown files and can be read by any tool or domain. This flat, predictable structure means domains can reference each other's outputs without special APIs or configuration.