feat: refresh shared skills catalog

This commit is contained in:
vasily committed 2026-10-30 12:40:16 +08:00
1 parent 98bb35e6fb
commit 418792d1ec
49 files changed
+2273 -2390

No files matched your search

+95 -69
View File
@@ -1,85 +1,111 @@
# global-skills
Personal skill repository shared by every coding agent on this host
(Antigravity/agy, Codex, OpenCode, Claude Code). Kept separate from JEV,
which remains its own project with its own skills.
Reusable workflows for coding agents: planning, debugging, API and database design,
security, UI, writing, performance benchmarking, and optional spec-driven development.
Skills help an agent complete the requested work with clear steps and appropriate verification.
## Sources
This repository is the canonical source for 20 shared skills on this host.
Installed skills link back to the source, so edits take effect without copying
files into each agent's directory. The workflows favor direct execution: use
existing context, preserve user work, and check only what the change needs.
Agents see skills from two sources:
## Install
| Source | Owner | Path |
|---|---|---|
| This repo | here | `~/Projects/work/global-skills/skills/` |
| JEV skills | JEV project | `~/Projects/work/JEV/.agents/skills/` |
Requires Bash, Python 3, and a filesystem supporting symbolic links. The supplied
installer targets Linux-style home directories and uses Python's standard library.
## Targets
`sync-skills.sh` maintains symlinks into each agent's skills directory:
- `~/.agents/skills` (OpenCode)
- `~/.codex/skills` (Codex)
- `~/.claude/skills` (Claude Code)
Antigravity reads both sources directly via `~/.gemini/config/skills.json`.
## Skill Catalog
All skills adhere to the 5-phase Skill Architect anatomy (`Phase 0: Setup` through `Phase 4: Output Execution & Verification`) with System One balance invariants.
### Planning & Review
- [`junior-to-senior`](skills/junior-to-senior/SKILL.md) — Adversarial staff-engineer review upgrading agent plans using live codebase inspection and SOTA research.
- [`debugging-workflow`](skills/debugging-workflow/SKILL.md) — Systematic root-cause isolation, minimal reproduction, and regression testing.
- [`emergency-procedures`](skills/emergency-procedures/SKILL.md) — Recovery protocols for broken agent loops, git tangle, and context drift.
### Writing & UI Craft
- [`fuck-slop`](skills/fuck-slop/SKILL.md) — Multi-genre de-slop pass eliminating statistical AI writing fingerprints.
- [`interface-kit`](skills/interface-kit/SKILL.md) — Authoritative implementation guide for UI craft, spring animations, and WCAG AA accessibility.
### Spec-Driven Development (SDD) Suite
- [`grill`](skills/grill/SKILL.md) — Calibrated plan interrogation before speccing.
- [`spec`](skills/spec/SKILL.md) — Sole mutator of `SPEC.md` managing goals, invariants, tasks, and bugs.
- [`caveman`](skills/caveman/SKILL.md) — Token-compression dialect (~75% reduction) for dense invariant specification.
- [`review`](skills/review/SKILL.md) — Adversarial pre-implementation spec refutation and gatekeeper.
- [`build`](skills/build/SKILL.md) — Single-threaded plan-to-execute loop with automated test oracles.
- [`check`](skills/check/SKILL.md) — Read-only drift detector verifying code against active invariants.
- [`backprop`](skills/backprop/SKILL.md) — Bug-to-spec feedback loop binding regression tests.
- [`deepen`](skills/deepen/SKILL.md) — Module design pass pulling complexity down and shrinking interfaces.
### Architecture & Security
- [`api-design`](skills/api-design/SKILL.md) — REST membranes, contract-first schemas, and boundary clamping.
- [`database-design`](skills/database-design/SKILL.md) — SQLite WAL persistence, repository abstraction, and keyset pagination.
- [`app-security`](skills/app-security/SKILL.md) — Four-Pillar upload defense, outbound SSRF guards, and secret masking.
- [`git-workflow`](skills/git-workflow/SKILL.md) — Atomic commit grouping, selective staging, and conventional commits.
### Meta & Infrastructure
- [`deliver-file`](skills/deliver-file/SKILL.md) — Push files and directories to the user's workstation over Tailscale SSH via `t3-deliver`.
- [`skill-architect`](skills/skill-architect/SKILL.md) — Standardized authoring, auditing, and maintenance of global agent skills.
## Usage
From a checkout:
```sh
./sync-skills.sh # after adding/updating/removing a skill
cd /path/to/global-skills
./sync-skills.sh --dry-run
./sync-skills.sh
./sync-skills.sh --check
```
Idempotent: re-links only what changed, never touches unrelated entries
(omarchy system skills etc.), warns on name collisions between the two
sources (this repo wins).
The default targets are:
## Adding a skill
| Target | Skill directory |
| --- | --- |
| OpenCode / shared agents | `~/.agents/skills` |
| Codex | `~/.codex/skills` |
| Claude Code | `~/.claude/skills` |
1. Create `skills/<skill-name>/SKILL.md` following the [sample-skill blueprint](skills/skill-architect/references/sample-skill.md).
2. Run `./sync-skills.sh`.
3. Commit.
Sync also includes JEV skills when `~/Projects/work/JEV/.agents/skills` exists.
It preserves unrelated files and symlinks, removes stale managed links, and rejects
source-name collisions. Antigravity uses separate source-path configuration.
## t3-deliver
See [installation and usage](docs/installation.md) for first-time setup, installing
one skill, custom targets, Antigravity configuration, updates, and troubleshooting.
`bin/t3-deliver` is symlinked to `~/.local/bin/t3-deliver`. It prints a
ready-to-paste `scp` command (Tailscale SSH) so the user can pull any file
from this host to their Windows machine. The `deliver-file` skill teaches
every agent to use it.
## Use
## T3 integration
Ask for the outcome in normal language. An agent can select a skill from its
name and description, or you can explicitly name the workflow:
Open this folder as a project in T3 Code to get a top-bar Action running
`sync-skills.sh` (Actions are project-scoped commands).
- “Use debugging-workflow to diagnose this failing request.”
- “Use interface-kit to improve this form using the existing components.”
- “Use junior-to-senior to review this implementation plan.”
- “Use benchmark-refactor to profile this module and evaluate optimizations.”
- “Use spec to write a specification, then implement task T1 with build.”
The spec suite applies when you choose that workflow. Ordinary bug fixes and
feature edits do not require a spec. Requests to review or report remain read-only.
Discovery and activation depend on the agent; this repository installs Markdown
instructions and links, without adding runtime hooks or model calls.
For projects with substantial architecture or design history, keep a concise,
project-owned context index pointing to the key code paths and design documents.
Load it when the task needs that history; avoid generating directory-by-directory
documentation unless maintainers will keep it accurate.
## Catalog
| Work | Skills |
| --- | --- |
| Plan and review | [grill](skills/grill/SKILL.md), [junior-to-senior](skills/junior-to-senior/SKILL.md), [review](skills/review/SKILL.md) |
| Adopted spec workflow | [spec](skills/spec/SKILL.md), [build](skills/build/SKILL.md), [check](skills/check/SKILL.md), [backprop](skills/backprop/SKILL.md), [caveman](skills/caveman/SKILL.md) |
| Fix and simplify | [debugging-workflow](skills/debugging-workflow/SKILL.md), [deepen](skills/deepen/SKILL.md), [emergency-procedures](skills/emergency-procedures/SKILL.md) |
| Architecture | [api-design](skills/api-design/SKILL.md), [database-design](skills/database-design/SKILL.md), [app-security](skills/app-security/SKILL.md), [benchmark-refactor](skills/benchmark-refactor/SKILL.md) |
| UI and writing | [interface-kit](skills/interface-kit/SKILL.md), [fuck-slop](skills/fuck-slop/SKILL.md) |
| Maintenance | [git-workflow](skills/git-workflow/SKILL.md), [deliver-file](skills/deliver-file/SKILL.md), [skill-architect](skills/skill-architect/SKILL.md) |
JEV supplies `context-architect`, `lint-architect`, `typesafe-ai`, `doc-architect`,
and `system-one-balance-protocol`. Its `anti-slop-editor` is a compatibility alias
to `fuck-slop`.
## Maintain
Content edits propagate through existing links immediately. Sync after adding,
removing, or moving a skill. Running agents may need a new session to refresh their
cached skill list or instructions.
```sh
python3 bin/validate-skills # metadata, local links, duplicate names; read-only
./sync-skills.sh --check # installed-link drift/conflicts; read-only
```
Validation is for catalog maintenance, not a preflight for everyday coding.
See [authoring and maintenance](docs/maintenance.md) for metadata, ownership,
verification conventions, and tool regression checks.
## Workflow conventions
[Shared workflow and verification](protocols/workflow.md) defines proportional
checks and preservation of user work. User and repository instructions take
precedence. Telemetry and pull requests follow [the telemetry protocol](protocols/telemetry.md).
Repository governance rules and boundary tiers adhere to [the agents template](protocols/agents-template.md).
References load on demand; there is no required phase anatomy, per-task commit,
separate review invocation, or blanket full-suite run.
Skills declare `scope: global`, `project`, or `alias`. Scope documents applicability;
it does not change a harness router by itself. JEV-dependent skills state their
project requirements. Some optional references assume a sibling JEV checkout.
## Host-specific file delivery
[deliver-file](skills/deliver-file/SKILL.md) uses `bin/t3-deliver` to print a command
for the user's Windows machine to pull files over Tailscale SSH. Its host address
is configured for this machine; adapt it before using delivery on another host.
The helper assumes `realpath` locally and OpenSSH scp with SFTP support remotely.
It prints a command and does not start a transfer.