accessibility-patterns
WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization
Create or update continuity ledger for state preservation across clears
Claude Code
$ npx -y skills add vibeeval/vibecosystem --skill continuity-ledger --agent claude-code
Codex
$ npx skills add vibeeval/vibecosystem --skill continuity-ledger -a codex -y
Cursor
$ npx skills add vibeeval/vibecosystem --skill continuity-ledger -a cursor -y
Gemini CLI
$ npx skills add vibeeval/vibecosystem --skill continuity-ledger -a gemini-cli -y
GitHub Copilot
$ npx skills add vibeeval/vibecosystem --skill continuity-ledger -a github-copilot -y
OpenCode
$ npx skills add vibeeval/vibecosystem --skill continuity-ledger -a opencode -y
Windsurf
$ npx skills add vibeeval/vibecosystem --skill continuity-ledger -a windsurf -y
name: continuity-ledger description: Create or update continuity ledger for state preservation across clears
> **Note:** This skill is now an alias for `/create_handoff`. Both output the same YAML format.
Create a YAML handoff document for state preservation across `/clear`. This is the same as `/create_handoff`.
**First, determine the session name from existing handoffs:**
ls -td thoughts/shared/handoffs/*/ 2>/dev/null | head -1 | xargs basename
This returns the most recently modified handoff folder name (e.g., `open-source-release`). Use this as the handoff folder name.
If no handoffs exist, use `general` as the folder name.
**Create your file under:** `thoughts/shared/handoffs/{session-name}/YYYY-MM-DD_HH-MM_description.yaml`, where:
**Examples:**
**CRITICAL: Use EXACTLY this YAML format. Do NOT deviate or use alternative field names.**
The `goal:` and `now:` fields are shown in the statusline - they MUST be named exactly this.
---
session: {session-name from ledger}
date: YYYY-MM-DD
status: complete|partial|blocked
outcome: SUCCEEDED|PARTIAL_PLUS|PARTIAL_MINUS|FAILED
---
goal: {What this session accomplished - shown in statusline}
now: {What next session should do first - shown in statusline}
test: {Command to verify this work, e.g., pytest tests/test_foo.py}
done_this_session:
- task: {First completed task}
files: [{file1.py}, {file2.py}]
- task: {Second completed task}
files: [{file3.py}]
blockers: [{any blocking issues}]
questions: [{unresolved questions for next session}]
decisions:
- {decision_name}: {rationale}
findings:
- {key_finding}: {details}
worked: [{approaches that worked}]
failed: [{approaches that failed and why}]
next:
- {First next step}
- {Second next step}
files:
created: [{new files}]
modified: [{changed files}]**Field guide:**
**DO NOT use alternative field names like `session_goal`, `objective`, `focus`, `current`, etc.** **The statusline parser looks for EXACTLY `goal:` and `now:` - nothing else works.**
**IMPORTANT:** Before responding to the user, you MUST ask about the session outcome.
Use the AskUserQuestion tool with these exact options:
Question: "How did this session go?" Options: - SUCCEEDED: Task completed successfully - PARTIAL_PLUS: Mostly done, minor issues remain - PARTIAL_MINUS: Some progress, major issues remain - FAILED: Task abandoned or blocked
After the user responds, mark the outcome:
# Mark the most recent handoff (works with PostgreSQL or SQLite)
PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "${CLAUDE_PROJECT_DIR:-.}")
cd "$PROJECT_ROOT/opc" && uv run python scripts/core/artifact_mark.py --latest --outcome <USER_CHOICE>After marking the outcome, respond to the user:
Handoff created! Outcome marked as [OUTCOME]. Resume in a new session with: /resume_handoff path/to/handoff.yaml
Each compaction is lossy compression—after several compactions, you're working with degraded context. Clearing + loading the handoff gives you fresh context with full signal.
A focused runtime for Claude Code. A bounded worker for Codex. Catalog (in repo): Default core: vibecosystem packages agents, skills and hooks for software work.
WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization
axe-core integration, WCAG 2.2 AA checklist, keyboard navigation testing, screen reader testing, and ARIA pattern validation.
Steam-style achievement system with XP, levels, streaks, and skill trees. Gamifies the development workflow. 25 achievements…
Framework for measuring and tracking agent response quality over time. Detects regressions before they reach production. Use when…
Agent ve skill dosyalarinin yapisal dogrulamasi. Frontmatter kontrol, naming convention, zorunlu bolum kontrolu, tutarlilik…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.