Init
Initialize the .singularskills/ directory for the current project. Set up the project configuration and choose which domains to activate.
Prerequisites
None — this is typically the first singularskills command you run in a new project.
Process
Check if .singularskills/ already exists:
- If it exists, read
.singularskills/config.md and show current configuration
- Ask if the user wants to update the configuration, or only the
Stack section of AGENTS.md (step 4b)
- If it doesn't exist, proceed with initialization
Ask the user:
- What is the project name?
- Which domains will you use? Present the full list:
- Design (component design with Figma integration)
- Research (Double Diamond discovery and validation)
- Development (plan, build, test, debug, review, ship)
- Marketing (RACE Framework campaigns)
- Branding (brand creation and compliance)
- Accessibility (WCAG-EM audits)
- Project Management (Scrum workflow)
- Coaching (domain-specific mentorship)
- Leadership (team development and management)
- Legal (contracts, compliance, governance)
Create the directory structure:
- Create
.singularskills/ root directory
- Create subdirectories for each selected domain
- Create
.singularskills/reports/ for cross-domain reports
Write the project configuration:
- Write
.singularskills/config.md with:
- Project name
- Active domains
- Date initialized
- Notes or goals (if the user provided any)
4b. Write the Stack section so the skills that build, test, lint, review or generate code know how this project is run. Take every value from the project's own files, never from a profile:
stack: from package.json (packageManager, and the versions of TypeScript, Next.js, React or other frameworks among its dependencies), Cargo.toml with rust-toolchain.toml (Rust toolchain and edition), pyproject.toml, go.mod or the equivalent
install, build, test, lint, format, typecheck, run: from package.json scripts, a justfile or a Makefile. For lint prefer the script that checks lint and format together (check, validate-style) over a bare lint; for format take only a variant that writes (format:fix, fmt, format --write) and leave format out otherwise; for test prefer the script CI runs. Leave out any key you cannot read, so the profile supplies it
rules: from the project's README, CONTRIBUTING or conventions file (a repo-conventions skill, a CLAUDE.md rules section), as short imperatives; leave it out when the project states none
layout: the top-level folders you see (for example apps/*, packages/*, crates/*, src/) and where tests live
profile: bun-react-ts when package.json has packageManager starting with bun@ and both next and react among its dependencies; profile: rust-gpui when a Cargo workspace member depends on gpui; otherwise no profile key
- Keep the shape flat: every key is one line of plain text (
stack, layout and rules are free text, never nested mappings or lists), and only the keys named above (stack, profile, install, build, test, lint, format, typecheck, run, layout, rules) appear; put stack first
- Write it as one fenced
yaml block under a ## Stack heading. Choose the file in this order: (1) if AGENTS.md or CLAUDE.md already has a ## Stack section, replace that section in place, in that file; (2) else if CLAUDE.md exists and AGENTS.md does not, write it into CLAUDE.md; (3) else write it into AGENTS.md, creating the file with the one-line intro "This project uses singularskills; the Stack section below tells its skills how to build, test and lint it." when it does not exist. Never create AGENTS.md next to an existing CLAUDE.md just for this section, and never leave two Stack sections across the two files.
- Suggest next steps:
- Based on selected domains, recommend which to start with
- Provide the first command to run
Output
The project configuration written to .singularskills/config.md and the ## Stack section written to AGENTS.md (or CLAUDE.md). Present the initialized structure and suggested next steps to the user.
1---2name: singular-init3description: Initialize singularskills in a project — create the workspace directory, choose which domains to activate and record the project configuration. Use when the user is starting to use singularskills in a new project or wants to change which domains are active in it.4metadata:5 source: https://skillmd.com/skills/bromso/singular-init6 disable-model-invocation: true7---89# Init1011Initialize the `.singularskills/` directory for the current project. Set up the project configuration and choose which domains to activate.1213## Prerequisites1415None — this is typically the first singularskills command you run in a new project.1617## Process18191. **Check if `.singularskills/` already exists:**20 - If it exists, read `.singularskills/config.md` and show current configuration21 - Ask if the user wants to update the configuration, or only the `Stack` section of `AGENTS.md` (step 4b)22 - If it doesn't exist, proceed with initialization23242. **Ask the user:**25 - What is the project name?26 - Which domains will you use? Present the full list:27 - Design (component design with Figma integration)28 - Research (Double Diamond discovery and validation)29 - Development (plan, build, test, debug, review, ship)30 - Marketing (RACE Framework campaigns)31 - Branding (brand creation and compliance)32 - Accessibility (WCAG-EM audits)33 - Project Management (Scrum workflow)34 - Coaching (domain-specific mentorship)35 - Leadership (team development and management)36 - Legal (contracts, compliance, governance)37383. **Create the directory structure:**39 - Create `.singularskills/` root directory40 - Create subdirectories for each selected domain41 - Create `.singularskills/reports/` for cross-domain reports42434. **Write the project configuration:**44 - Write `.singularskills/config.md` with:45 - Project name46 - Active domains47 - Date initialized48 - Notes or goals (if the user provided any)49504b. **Write the Stack section** so the skills that build, test, lint, review or generate code know how this project is run. Take every value from the project's own files, never from a profile:51 - `stack`: from `package.json` (`packageManager`, and the versions of TypeScript, Next.js, React or other frameworks among its dependencies), `Cargo.toml` with `rust-toolchain.toml` (Rust toolchain and edition), `pyproject.toml`, `go.mod` or the equivalent52 - `install`, `build`, `test`, `lint`, `format`, `typecheck`, `run`: from `package.json` scripts, a `justfile` or a `Makefile`. For `lint` prefer the script that checks lint and format together (`check`, `validate`-style) over a bare `lint`; for `format` take only a variant that writes (`format:fix`, `fmt`, `format --write`) and leave `format` out otherwise; for `test` prefer the script CI runs. Leave out any key you cannot read, so the profile supplies it53 - `rules`: from the project's README, CONTRIBUTING or conventions file (a repo-conventions skill, a `CLAUDE.md` rules section), as short imperatives; leave it out when the project states none54 - `layout`: the top-level folders you see (for example `apps/*`, `packages/*`, `crates/*`, `src/`) and where tests live55 - `profile: bun-react-ts` when `package.json` has `packageManager` starting with `bun@` and both `next` and `react` among its dependencies; `profile: rust-gpui` when a Cargo workspace member depends on `gpui`; otherwise no `profile` key56 - Keep the shape flat: every key is one line of plain text (`stack`, `layout` and `rules` are free text, never nested mappings or lists), and only the keys named above (`stack`, `profile`, `install`, `build`, `test`, `lint`, `format`, `typecheck`, `run`, `layout`, `rules`) appear; put `stack` first57 - Write it as one fenced `yaml` block under a `## Stack` heading. Choose the file in this order: (1) if `AGENTS.md` or `CLAUDE.md` already has a `## Stack` section, replace that section in place, in that file; (2) else if `CLAUDE.md` exists and `AGENTS.md` does not, write it into `CLAUDE.md`; (3) else write it into `AGENTS.md`, creating the file with the one-line intro "This project uses singularskills; the Stack section below tells its skills how to build, test and lint it." when it does not exist. Never create `AGENTS.md` next to an existing `CLAUDE.md` just for this section, and never leave two Stack sections across the two files.58595. **Suggest next steps:**60 - Based on selected domains, recommend which to start with61 - Provide the first command to run6263## Output6465The project configuration written to `.singularskills/config.md` and the `## Stack` section written to `AGENTS.md` (or `CLAUDE.md`). Present the initialized structure and suggested next steps to the user.