By darkmatter
Darkmatter's team-wide shared skills catalog, auto-discovered from skills/.
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.
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.
Use when configuring or operating Beads Linear sync in Darkmatter repos, especially choosing Linear team/project scope, mapping Beads prefixes to Linear identifiers, handling himitsu API keys, or dry-running bd linear sync safely.
Onboard a darkmatter repo onto beads (`bd`) as the standard task tracker and persistent agent memory store, per ADR-0001. Triggers when a repo has no `.beads/` directory, when `bd` is not installed, when the user asks to "use beads here", "set up beads", "add beads to this repo", "enable beads linear sync", or when an agent needs `bd ready` / `bd remember` and finds the workspace unconfigured. Also triggers when wiring beads to Linear for a team that already uses Linear. Do NOT trigger for routine `bd create` / `bd close` work in an already-initialized repo, or for non-darkmatter projects that have opted out of this convention.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Team-wide LLM preset infrastructure for the darkmatter umbrella. OpenCode is the preferred client, but this repo stays source-oriented: shared assets live here and are synced into OpenCode, Claude-compatible, Codex, and generic agent locations as needed.
This repo ships four things:
presets/) — installable source packs for LLM clients.skills/) — installed across all darkmatter projects via Nix Home Manager, or as a Claude Code plugin (see Claude Code plugin marketplace).template/) — .agent/, config, and shims to stamp into a new project repo.scripts/) — generators, installers, sync scripts, and validation helpers.It is provider-agnostic. Skills and .agent/ content target any agent tool (Claude Code, Codex, OpenCode, Cursor, Aider, etc.) by following the cross-vendor AGENTS.md convention plus the per-vendor shims (CLAUDE.md, .cursorrules).
darkmatter/skills/
├── .claude-plugin/ ← Claude Code marketplace + plugin manifests
├── README.md ← this file
├── flake.nix ← Nix entry; exports the Home Manager module
├── home-manager.nix ← HM module that wires skills/ into agent CLIs
├── presets/ ← installable source packs, especially OpenCode
├── skills/ ← team-wide shareable skills (the catalog)
├── template/ ← the per-project bootstrap (stamped by new-project.sh)
├── scripts/
│ ├── new-project.sh ← stamp template/ into a target dir
│ └── validate-skill.sh ← sanity-check skills/ catalog
├── evals/
│ ├── skills/ ← Promptfoo behavior evals (LLM decision checks, CI)
│ └── prompt-tests/ ← real-repo opencode evals (local/manual only)
└── docs/
├── catalog.md ← what's in skills/
└── new-project-guide.md ← walkthrough for bootstrapping a project
The skills catalog is also installable as a Claude Code plugin — no Nix required. Inside Claude Code:
/plugin marketplace add darkmatter/skills
/plugin install darkmatter-skills@darkmatter
.claude-plugin/marketplace.json defines the marketplace and lists the repo root
(./) as a single plugin; .claude-plugin/plugin.json is that plugin's manifest.
Claude Code auto-discovers every skills/<name>/SKILL.md, so adding a skill to the
catalog adds it to the plugin with no extra registration. Validate changes with
claude plugin validate ..
The Nix Home Manager module remains the primary distribution path on darkmatter machines; the marketplace is for Claude Code users outside that setup (or for trying the catalog before wiring up Nix).
OpenCode-native assets live in presets/opencode/. Shared cross-client
instructions live in presets/base/, and shared skills remain in skills/.
See docs/opencode-layout.md for the source-to-install mapping.
Use this table before adding a new instruction, skill, command, hook, or tool. The goal is to keep always-on context small while still making reusable behavior discoverable.
npx claudepluginhub darkmatter/skills --plugin darkmatter-skillsEditorial "Web Designer" bundle for Claude Code from Antigravity Awesome Skills.
Frontend design taste skills including brutalist, minimalist, soft, redesign, stitch, and more
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Frontend design skill for UI/UX implementation
Memory compression system for Claude Code - persist context across sessions
Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth