Capture the spark
Start with what you want to make. The Idea stage helps clarify the purpose before the details race ahead.
A development system for ideas with direction
Keep the spark.
Keep the spark.
Build it with purpose.
ATS-AIOS helps turn a spontaneous idea into a coherent product—by giving AI-assisted development a clear path, connected roles and useful checks along the way.
Still creative. More deliberate about what happens next.
From spark to something solid SYSTEM FLOW
THE STARTING POINT“I have an idea…”•••
01IdeaFind the heart of it✓
02DesignWork out how it should feel✓
03ImplementBuild from a shared plan•••
04ConfigureBring the product to life○
Direction stays connectedIdea → Design → Implement → Configure
A better way to vibe-codeSpontaneity is the spark.
Spontaneity is the spark.
Direction makes it buildable.
Fast ideas are exciting. But when each new thought skips ahead, details get missed and decisions drift. ATS-AIOS gives those ideas a route through the right questions, design and checks—so the result holds together.
Connect the decisions
Design, architecture and planning make assumptions and dependencies visible while there’s still time to address them.
Give each step a job
Agents and reusable standards help turn an agreed direction into focused, reviewable work.
A peek inside the app
Your projects, still moving.
The Pocket Companion is a small place to check in on companion games from the ATS-AIOS app. Here, you’re seeing a website preview—not a running tool.
Explore the Pocket Companion guide01 04
COMPANION PREVIEW · CONCEPTSeven Is WatchingUnity project
Illustrative only · not connected to the appWant the wider picture?
Explore ATS-AIOS capabilities See the system behind the build.
The working methodAn idea gets a path.
An idea gets a path.
The path keeps its purpose.
ATS-AIOS uses a simple development model to keep intent, design and implementation connected. It gives work structure without taking the creative spark away.
Idea
Explore the concept, find what matters and shape a clear starting point.
Idea BriefDesign
Define the experience, the behavior and the structure before building.
Design + ArchitectureImplement
Plan the work, assign focused responsibilities and build in connected steps.
Plans + working productConfigure
Populate and tune the implemented product with its intended content and settings.
Completed productStructure serves the idea.
Not every project needs the same depth or pace. The point is to bring in the right thinking before a skipped decision becomes expensive rework.
A connected workforce
Clear roles. Shared direction.
ATS-AIOS has agents for meaningful work and reusable skills, standards and templates for bounded procedures and quality. They work from the same project direction instead of inventing separate versions of it.
Agents
Own substantial responsibilities such as exploring an idea, defining a design, shaping architecture or reviewing evidence.
Skills & standards
Bring repeatable procedures and quality expectations to focused tasks.
Templates
Give important project artifacts a structure people and agents can follow.
Grounded in real project requirements
Explore the examples See four ways the process makes gaps visible.
A growing capability map
What ATS-AIOS can help with.
This page describes capabilities from the system’s current agents, skills, standards and templates. As those sources evolve, this guide can grow with them—while showing what is defined, applied and validated.
SOURCE-LED OVERVIEWReviewed snapshot · 23 Sep 2026
01DEFINED
Shape ideas
Clarify a concept, challenge assumptions and prepare an Idea Brief that can guide the next stage.
Idea Agent · Idea Brief template02DEFINED
Design experiences
Make behaviors, rules, interactions, flows and feedback clear enough to carry into technical design.
Design Agent · Design Standard03DEFINED
Connect the architecture
Set responsibilities, data ownership, dependencies and boundaries that support the approved design.
Architect · Architecture Standard04DEFINED
Plan implementation
Break work into modules, define requirements, sequence dependencies and prepare bounded handoffs.
Implementation Coordinator · IDIC templates05DEFINED
Build for a platform
Route approved implementation work to platform specialists for focused execution and integration.
Unity · Roblox · Electron specialists06DEFINED
Check evidence
Review work against approved criteria, identify gaps and report what the available evidence does—and doesn’t—show.
Quality Agent · evidence-led review07DEFINED
Maintain project continuity
Keep project state, decisions and handoffs readable so the next work session can start from the right place.
Project Agent · project coordination↗GROWING
More as the system grows
New and revised capabilities can be added here after their owning ATS-AIOS sources are reviewed.
Changes are curated; updates are not automatic.Capability levels shown on this page describe the current source definition. Project application and implementation validation need their own traceable evidence. ATS-AIOS helps surface gaps; it cannot guarantee bug-free output.
Small gaps. Expensive surprises.
Catch the “oh, we forgot…” earlier.
These examples come from approved Against the Horde module requirements. They show how ATS-AIOS makes obligations explicit and connected—not failures that happened in the game, or tests that have already passed.
4 SOURCE-BACKED EXAMPLESSpecified in project requirements
A setting never makes it into the player save.
Approved M08 profile requirements explicitly include settings among durable profile data and distinguish them from run-only ranks, slots and combination marks that reset. The boundary is visible in the contract before implementation planning.
Source reference: Against the Horde M08 · Profiles & Shard TransactionsA paid Continue revives the player but mishandles currency or records.
Requirements define debit-before-revival ordering, safe retries and exclusion from unassisted records. M12 also requires cost and record consequences to be visible before confirmation.
Source references: Against the Horde M07 · Recovery & Continue; M08; M12A new action works on keyboard but is unreachable on touch or controller.
M12-R02 lists critical actions that must be reachable on keyboard/mouse, controller and touch, with clear accepted or rejected feedback.
Source reference: Against the Horde M12 · Cross-Device PresentationA save is called complete because it worked in an editor session.
M14 requires module obligations to map to evidence or a stated gap, including published-client persistence and rejoin validation. An editor check alone is not published persistence acceptance.
Source reference: Against the Horde M14 · Integration & Quality EvidenceThese are requirement-based illustrations, not a claim that these failures happened or that runtime acceptance has passed. Source documents remain in the ATS-AIOS workspace and are not exposed by this website guide.
A guide to the real app
Explore the ATS-AIOS workspace.
This is a visitor-facing guide inspired by the app’s areas. It helps explain where things live and what they’re for. The real ATS-AIOS app is where its tools and workflows operate.
Guide preview · no app connection
GUIDE SKELETON
Home
The app’s starting space and its current role.
Read guide → GUIDE SKELETONProjects
How a project’s status and current stage are organized.
Read guide → GUIDE SKELETONWorkforce
Agents, sub-agents and the reusable capabilities around them.
Read guide → GUIDE SKELETONLibrary
Shared resources, what they’re for and how people use them.
Read guide → GUIDE SKELETONSystem
System-wide tools and rules, explained in visitor-friendly language.
Read guide → GUIDE SKELETONOperations
Operational views such as the Tracker and companion features.
Read guide →This guide doesn’t show the workspace folders.
It explains what app areas are for without publishing the private working structure or copying the app’s actual tools into a website.
Operations · Desktop
Pocket Companion.
A quick window into one companion game at a time. In the app, this is a destination of its own, separate from Home. This website shows an illustrative preview.
Concept preview · no live game, save or app connectionAPP AREA GUIDEA small check-in.
A small check-in.
A path into more.
The app design describes a page for choosing a companion game, viewing one active game widget and opening that game’s detailed page. Widgets may be view-only or later support a small set of game-specific quick interactions.
The skeleton design uses clearly marked concept regions until those functions are implemented. This web preview only cycles through project names to show the idea.
Back to app areas →POCKET COMPANIONCONCEPT
ACTIVE GAME PREVIEWSeven Is WatchingUnity project · Illustrative
Game selection ConceptWidget state Not connected
App guide · HomeGUIDE SKELETON← All app areas
The app Home area.
This guide page will explain the current Home surface and its available destinations. The website’s own Home is a product introduction and Pocket Companion showcase; it is not a reproduction of the app’s Home.
Guide content in progress
Current app design keeps Home distinct from Operations features. This page will expand as the app experience and approved documentation develop.
App guide · WorkspaceGUIDE SKELETON← All app areas
Projects.
How the app helps you enter a project workspace and understand its current direction.
Guide content in progress
This page will explain the app’s project view without exposing the website visitor to the real workspace folder tree.
App guide · CapabilitiesGUIDE SKELETONExplore current capabilities →
Workforce.
Learn how agents, sub-agents and reusable capabilities contribute to the work.
Guide content in progress
The public capability overview is available now. A deeper walkthrough of the app’s Workforce views will be added as those screens are ready.
App guide · Shared resourcesGUIDE SKELETON← All app areas
Library.
A visitor-friendly explanation of how reusable material is collected, described and traced back to its source.
Guide content in progress
This guide explains the Library’s purpose. It does not display the actual files, folders or internal paths.
App guide · SystemGUIDE SKELETON← All app areas
System.
Understand where system-wide tools and shared rules fit into the ATS-AIOS workspace.
Guide content in progress
Specific tool explainers will be added from current, approved app and system sources.
App guide · OperationsGUIDE SKELETON← All app areas
Operations.
Operational views help coordinate defined slices of ATS-AIOS work. Each explainer will make its purpose and boundaries clear.
Guide content in progress
Explore the Pocket Companion guide. Other operational page guides will follow as their current behavior is documented.