Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Absolute Init

One-time setup that detects your project's stack, interviews you for a handful of preferences, and writes the shared JSON config every other absolute-* command reads.

AutomationIntermediate★ 211⑂ 31AI score 9/10Last updated: Jul 6, 2026

What it does

  • Detects package manager, language/runtime, test/lint/typecheck/format/build scripts, CI file and default branch, storing them as the project's own script form (npm test, make lint) so cached commands match CI.
  • Optionally detects a UI block (framework, styling, icon library, component lib, tokens path) and a docs block (fumadocs, Docusaurus, Starlight, MkDocs, VitePress, Mintlify) — omitted entirely when not applicable.
  • Asks only 4-6 questions via structured choices: output style, autonomy/gating, TDD strictness, spec output dir, and which command families you use.
  • Writes .absolute.config.json (team-shared, meant to be committed) plus an optional ~/.absolute/config.json with global defaults and per-project overrides, with a documented precedence and merge order. Existing config is summarized and merged, never clobbered; it never commits for you.

Who it's for

  • Users of the absolute command suite (work, spec, ui, simplify, docs, health family) tired of re-detection on every run.
  • Teams that want one canonical test/lint command and convention set checked into the repo.
  • Anyone who wants different autonomy or TDD rigor per project without repeating it each session.

Examples

  1. Fresh repo: run "absolute init" → it detects pnpm + TypeScript + vitest, asks about output style/autonomy/TDD, writes .absolute.config.json and reminds you to commit it.
  2. Swapped npm for pnpm or renamed the default branch: re-run init → it prints current values and updates only what changed.
  3. Prefer terse everywhere but normal in one repo: store the default globally and add a projects["/path/to/repo"] override.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/maddhruv/absolute/HEAD/skills/absolute-init/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/absolute-init folder from the GitHub repo maddhruv/absolute into my ~/.claude/skills/absolute-init/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/maddhruv/absolute.git /tmp/absolute && mkdir -p ~/.claude/skills && cp -r /tmp/absolute/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and go to a working directory.
  2. Clone the repo: git clone https://github.com/maddhruv/absolute.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy the skills in: cp -r absolute/skills/* ~/.claude/skills/ (copying the whole suite is recommended, since other absolute commands consume this config).
  5. Start Claude Code inside the project you want to configure.
  6. Type absolute init (or "set up absolute") and answer the questions one at a time.
  7. Review the generated .absolute.config.json and commit it yourself — the skill deliberately never commits.
View source on GitHub ↗License: MIT