Agent skills & workflows
Agent skills & workflows
Section titled “Agent skills & workflows”This section is the handbook for day-to-day engineering rhythm: pull requests, releases, GitHub hygiene, and how those practices connect to the roadmap in this site (single source of truth for planning and delivery narrative).
Principles
Section titled “Principles”- Planning and roadmap status live in Roadmap (this docs site). GitHub is an operational mirror: PRs, releases, and short-lived tracking—not a second backlog you must reconcile by hand.
- Executable Cursor skills are personal: they live under
~/.cursor/skills/<skill-name>/SKILL.mdon your machine. They are available in a multi-repo workspace no matter which repository folder is active. - Vibe-coding / AI-generated changes: the human gate is verification—does the app behave, does the environment work, do critical paths pass—not line-by-line code review as the default bar.
Where to go next
Section titled “Where to go next”| Goal | Start here |
|---|---|
| Paths on disk, docs URLs, GitHub touchpoints | Where things live |
| How umbrella + focused skills fit together | How skills interact |
| “I want to…” cheat sheet | Workflow index |
| Commit / push with a confirm step (any repo) | Ship ready |
| Branch/PR habits for multi-repo features | PR and branching |
| Releases tied to roadmap “Shipped” | Releases and changelog |
| Issues, stale queues, legacy repos | GitHub hygiene |
| Why roadmap wins over GitHub issues | Roadmap authority |
Relation to GitHub
Section titled “Relation to GitHub”The Sylva org on GitHub (https://github.com/sylva-ag) should stay clean and tidy: meaningful commits and release notes, issues either current or closed with a pointer back to these docs. See GitHub alignment with roadmap for the explicit split of responsibilities.