FlowKy is eleven features, and none of them is the product. The product is the loop they close: your agent knows the repo, follows the standards, gets the work, and the finished work reaches a page you can show. This is that loop, in the order that makes each step feed the next. In VS Code, the same seven steps are a guided walkthrough — open the command palette and run "Welcome: Open Walkthrough", then pick FlowKy.
1. Connect (once)
Sign in from the extension (FlowKy: Connect). This unlocks the standards catalog, task sync and your project page. Your code, prompts and API keys never pass through FlowKy — the account is for sync, not traffic.
2. Kick off the project
Be SOTA — start this project right. The free kickoff bundle walks the decisions that are cheap on day one and expensive on day ninety, and records each one as made or open in .flowky/sota/reports/. Deferring a decision is fine; deferring it in writing is the point.
3. Equip your agent with the standards
Be SOTA — equip. Every playbook your plan can read is fetched into .flowky/sota/ and installed as a Claude Code skill (auto-loaded by relevance) plus an AGENTS.md section for Cursor, Copilot and Codex. From this moment your agent applies the standards without FlowKy in the loop — and a playbook you edit is what it reads next session.
4. Give the agent a map
Generate the project configuration: the codebase map, the rules, the project-map skill. This is the memory your agent loses between sessions, rebuilt from the code itself and checked against HEAD at every session start — it tells you how stale it is instead of being confidently wrong.
5. Audit against the standards
Audit all. Every applicable check runs; every finding names the published standard it enforces (all of them readable at flowky.ai/sota). Findings have an honest lifecycle — open, fixed, withdrawn, dismissed — and re-audits reconcile instead of re-announcing.
6. Hand findings to the agent
From the findings panel, Fix with FlowKy sends the file, the line and the standard straight to your coding agent — Claude Code if present, the CLI if not, the clipboard as a last resort. You review the diff; the agent types; the standard already did the thinking.
7. Close the loop on flowky.ai
Sync sends tasks, captures and audit digests to the project page — the same page the browser extension feeds with full-page captures and recorded flows. Work found becomes work routed; work finished becomes a portfolio a buyer can check.
Then it repeats without ceremony
Day to day you touch three of the seven: the agent works (with the map and the skills it now has), you audit when it matters, you sync when something should reach the project page. Kickoff and equip are once per project; connect is once per machine. When you learn something the standards missed, Be SOTA — record what we just learned writes it into a playbook of your own — and from then on your agent knows it too.