darkmatter

@darkmatter source repo

41 skills
0 followers
16 hours ago last updated

▌
Docs · darkmatter bundle
Prelude agent guide

0
installs
▌
Prelude · darkmatter
Context map of Prelude, the Nix devshell UI suite (MOTD banner, x command catalogue, docs viewer, themed prompt). Use for any task in a prelude-enabled repo, or when the user mentions prelude, x/motd/docs commands, the prelude wizard, or its flake-parts options. Enriches the task with accurate public-interface knowledge; never installs or reconfigures on its own.

0
installs
▌
Prelude Docs · darkmatter
Manage a consumer repo's Prelude docs viewer content — prelude.docs.pages, groups, mdSplit README hero, and generated nixosOptions pages. Use when adding or fixing project documentation shown by `docs` / `x docs`, wiring the README landing page, or generating option docs.

0
installs
▌
Prelude Just · darkmatter
Use when authoring or editing Justfile recipes in a repository wired to Prelude, when the user asks to add just recipes or make them discoverable in the x menu, or when a recipe needs descriptions, typed arguments, groups, aliases, or module namespacing. Covers recipe authoring for Prelude's runtime Justfile import and verification through x.

0
installs
▌
Prelude Install · darkmatter
Install and configure Prelude (darkmatter/prelude) in any repository — run the setup wizard, wire the flake-parts module into an existing or new flake, activate packages.prelude-shell in the devshell, and verify with real smoke checks. Use for adding devshell UI (MOTD, x command picker, docs viewer, themed prompt), integrating the generated prelude.nix sidecar, or activation questions (nix develop, direnv, lorri).

0
installs
▌
Flue · darkmatter
Use when working with flue framework

0
installs
▌
Advisor · darkmatter
Instructions when acting as an Advisor to another Agent

0
installs
▌
Alchemy · darkmatter bundle
Configure, develop, deploy, review, and troubleshoot Alchemy v2 infrastructure for Darkmatter TypeScript/Effect apps. Triggers for alchemy.run.ts, alchemy dev, public preview URLs, webhook testing, Cloudflare/AWS providers, stages, profiles, state stores, bindings, CI deploys, or examples from alchemy-run/alchemy-effect. Prefer Alchemy for new org deploys. Do NOT trigger for unrelated blockchain Alchemy APIs unless the user explicitly means alchemy.run.

0
installs
▌
Diagnose · darkmatter bundle
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → verify. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

0
installs
▌
Agent Browser · darkmatter bundle
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

0
installs
▌
UI UX Pro Max · darkmatter bundle
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.

0
installs
▌
Caveman Commit · darkmatter
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

0
installs
▌
Codebase Cleanup · darkmatter bundle
Multi-pass refactor / code-quality cleanup designed to be dispatched as 8 specialist subagents (one per cleanup concern), each running a research → critical-assessment → high-confidence-implementation cycle. Triggers on "clean up the codebase", "tech-debt pass", "refactor for quality", "find dead code", "remove AI slop", or any explicit request for a comprehensive quality sweep. Do NOT trigger for narrow targeted fixes ("remove this one function") or for net-new feature work.

0
installs
▌
Effect Typescript · darkmatter bundle
Effect is a hard default unless the codebase explicitly states it. Use this skill when writing any Typescript code.

0
installs
▌
Dm Skill Creator · darkmatter bundle
Create new team-wide skills inside the darkmatter/skills repo following its conventions (skills/<name>/SKILL.md, no external deps, self-contained, validated by scripts/validate-skill.sh, registered in docs/catalog.md, distributed via the flake's home-manager module). Triggers when the user asks to "add a skill", "create a skill", "promote this into a skill", "make a darkmatter skill", or wants to generalize a workflow used across multiple darkmatter projects into the shared catalog. Also triggers when editing or refactoring an existing skill in this repo. Do NOT trigger for personal/project-local skills (those live elsewhere) or for skills outside the darkmatter/skills catalog.

0
installs
▌
Definition Of Done · darkmatter bundle
Guides agents and users to define a clear Definition of Done for agentic tasks, ensuring outcomes are recognized and satisfying.

0
installs
▌
Sops Secret Access · darkmatter
Use when a repo stores tool config, API keys, registry URLs, environment variables, or component registry settings in SOPS-encrypted files such as components.sops.json or secrets/*.sops.json.

0
installs
▌
Kickoff Dm Design · darkmatter
Manual-invocation skill — run only when the user explicitly asks for "kickoff-dm-design" or invokes it as a slash command. Do not auto-trigger on adjacent topics. Inverted-flow design-room kickoff for Darkmatter teammates. Operator creates a Claude Design project manually, drops the URL — this skill creates the Linear ticket, posts the kickoff to #design-room, and cross-links Linear ⇄ Slack ⇄ Claude Design. Non-interactive — never asks for a brief, team, or confirmation. Derives screen name + brief from the URL itself. Idempotent on rerun.

0
installs
▌
When To Write Tests · darkmatter
Decide whether to add a test. Use before writing or requesting tests. Default is no new test. Prefer a few end-to-end happy-path tests of the public contract over unit tests of internals.

0
installs
▌
End Of Turn Review · darkmatter bundle
Run a GPT-5.5 critique of the work just produced in the current turn — applied diffs, proposed plans, or both. Triggers at end-of-turn (via Stop hook) or on explicit request ("review what you just did", "critique this plan", "second-opinion this before I commit"). Returns a verdict (LGTM / notes / block) plus specific issues with file:line citations. Do NOT trigger for trivial 1-3 line changes, doc-only edits, or read-only research turns.

0
installs
▌
Continuous Learning · darkmatter bundle
Runtime learning policy — automatically extracts reusable patterns from sessions into learned skills. Not an ordinary task skill; consumed by the agent client at session end.

0
installs
▌
Run Meeting Summary · darkmatter bundle
Manual-invocation skill — run only when the user explicitly asks for "run-meeting-summary" or invokes it as a slash command. Do not auto-trigger on adjacent topics. Resolve meeting artifacts from loose requests, pasted text, local files, or provider connectors; draft a company-safe Obsidian summary; require a submit/edit/discard review gate before writing.

0
installs
▌
Caveman · darkmatter
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

0
installs
▌
Darkmatter Repo Setup · darkmatter bundle
Use when setting up a new repo, onboarding an existing repo to darkmatter standards, running a compliance check, or when the user says "set up this repo", "bring repo up to standards", "apply template", or "audit repo". Checks and installs the org TypeScript toolchain (Bun, tsgo, oxlint/oxfmt, Vitest), Nix flake-parts devshell, ops/ surface, CI pipeline, and AGENTS.md conventions.

0
installs
▌
Shadcn Registry First · darkmatter
Bias UI work toward installing existing components from configured shadcn registries (the free @shadcn registry and the paid @shadcnblocks block registry) before hand-rolling them. Triggers when building or restyling React UI in a project that has a components.json with registries configured — heroes, navbars, footers, pricing tables, feature grids, dashboards, forms, auth screens, marketing sections, data tables, and other common blocks. Use the shadcn MCP tools to search, preview, and add, and always assemble at least three buildable variations with a side-by-side comparison surface before settling on one. Do NOT trigger for genuinely bespoke or domain-specific components that no registry would carry, for non-React stacks, or for projects with no registry configured.

0
installs
▌
Compress · darkmatter bundle
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"

0
installs
▌
Choose Dev Entrypoints · darkmatter
Choose the right dev-environment entrypoint and responsibility boundary across Nix, Just, Bun, Turborepo, package scripts, shellHook, and ./scripts. Triggers when the user asks which command should run dev/build/test/install/codegen, whether to put work in nix develop or shellHook, how to split responsibilities between just, bun, turbo, and scripts, or how to make dev environments lazy, cacheable, and understandable. Do NOT trigger for ordinary implementation work or Nix flake layout refactors. In a TypeScript-only repo, ops scripts are TypeScript (ADR-0012), not bash.

0
installs
▌
Nix Flake Organization · darkmatter
Use when reorganizing Nix flakes, flake-parts outputs, NixOS modules, nix-darwin modules, or Home Manager modules into a thin flake/ public surface with implementation under src/.

0
installs
▌
Darkmatter TS Toolchain · darkmatter
The darkmatter TypeScript toolchain contract - Bun (never npm/pnpm), tsgo typecheck, vitest, oxlint/biome, changesets, Effect for I/O, Alchemy deploys (wrangler.toml is prohibited), merge-queue mains, and the no-tiny-functions rule. Use when writing, fixing, building, or shipping TypeScript in any darkmatter repo (platform, nixmac-web, omp-chat, genesis): "fix TS errors", "make CI green", "add a package", "deploy this worker", lockfile complaints, or choosing libraries for I/O-heavy code. Do NOT use for generic TS style (coding-standards) or deep Effect patterns (effect-typescript) — this skill is the org-specific toolchain glue around those.

0
installs
▌
Repository Organization · darkmatter
Organize darkmatter repositories, READMEs, agent context, docs, scripts, skills, and ADRs into the right durable locations. Triggers when deciding where something belongs, restructuring repo layout, adding always-follow rules, or documenting architectural decisions. Do NOT trigger for Nix flake-specific layout work; use nix-flake-organization instead.

0
installs
▌
Test Driven Development · darkmatter bundle
Use when the user asks for TDD, test-first, red-green-refactor, or an end-to-end happy-path test of a public contract. Do not use for ordinary implementation, refactors, helpers, or comment-only changes.

0
installs
▌
Darkmatter Design System · darkmatter bundle
Default design system — darkmatter's dark-first, terminal-inspired design system , built on Tailwind CSS v4, React 19, and Radix UI. Use this as the default design system when working in an app that does not already have an established design system or guidelines. Use it for dashboards, trading/monitoring consoles, forms, tables, settings, navigation, or any screen that should look and feel like darkmatter's brand. This is the canonical source for darkmatter components, tokens (the OKLCH --n-* ramp), theming, and layout — prefer it over generic shadcn/ui.

0
installs
▌
UI Component Architecture · darkmatter bundle
Keep React screens thin and reusable UI in its own package, separate from app screens. Triggers when authoring or restyling a page, route, screen, or component in an app that has a shared UI package — especially when a file is trending toward walls of plain <div className="..."> Tailwind markup. Bias toward reusing existing primitives in that package and graduating new reusable units into it, while avoiding premature over-extraction. Do NOT trigger for non-React code, for single-package apps with no shared UI package, or for editing the internals of one existing component. The package name is per-repo (see ADR-0013); do not require @repo/ui or @native/ui.

0
installs
▌
Keep Codebase Maintainable · darkmatter bundle
Use when cleaning a codebase, not shipping features.

0
installs
▌
Run UI Registry Variations · darkmatter bundle
Manual-invocation skill — run only when the user explicitly asks for "run-ui-registry-variations" or invokes it as a slash command. Do not auto-trigger on adjacent topics. Force UI work through shadcnblocks, Aceternity, or https://shadcn.darkmatter.io; validate private registry access before use; build exactly three user-reviewable variations.

0
installs
▌
Vercel React Best Practices · darkmatter bundle
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

0
installs
▌
Caveman Review · darkmatter
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

0
installs
▌
Executing Plans · darkmatter
Use when you have a written implementation plan to execute in a separate session with review checkpoints

0
installs
▌
Darkmatter Gitops Conventions · darkmatter
Safe-change playbook for the darkmatter/gitops repo — validation before commit (kubeconform with CI-identical flags, yq for YAML manifests, jq for SOPS JSON, git diff --check), sha-pinned images, KSOPS/SOPS secret editing rules, rollback via revert, and how ArgoCD reconciles. Use for ANY change to darkmatter/gitops (manifests, Helm values, apps/*.yaml, secrets), when asked to bump an image tag, wire a secret, or roll back a deploy. Also use when tempted to kubectl apply/edit/patch anything — the answer is no.

0
installs
▌
Systematic Debugging · darkmatter bundle
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

0
installs
▌
Subagent Driven Development · darkmatter bundle
Use when executing implementation plans with independent tasks in the current session

0
installs

41 published skills