ato

Engineering Community

Skill notes

Step 1: Draft The Architecture

Capture user intent as ato code immediately. Start with a clean high-level architecture and only stop to ask batched design questions when there are real unresolved decisions. Focus on: What the system is supposed to do The main functional blocks The important interfaces and voltage domains

Step 2: Write The Spec

The spec IS the design file at a high level of abstraction. As you implement, you fill in real components and wiring. The file grows; the structure stays. Key principles: Good naming — name modules by their role in the system, not implementation topology (see Section 1.1). Module boundaries should encapsulate common functionality to avoid duplication at the top level. Use high-level interfaces (ElectricPower, I2C, SPI, UART, ElectricLogic) instead of low-level electrical connections where possible.

Step 3: Resolve Open Decisions

Present the user with the current architecture and any real unresolved decisions: List the modules and their responsibilities. Show the interface connections between modules. Highlight any key decisions or trade-offs made. Call out any assumptions or areas where alternatives exist.

Step 4: Implement Detailed Design

Now fill in the spec with real components, wiring, and constraints. This step covers package search, part selection, and detailed wiring.

4a: Find existing packages

Search the atopile package registry before building from scratch. Tools: packages_search → packages_install → package_ato_read to inspect public interface. Also check stdlib_list for built-in modules. Prefer reusing a well-tested package over writing a new driver module.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@atopile · MIT
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Draft The Architecture

Capture user intent as ato code immediately. Start with a clean high-level architecture and only stop to ask batched design questions when there are real unresolved decisions. Focus on: What the system is supposed to do The main functional blocks The important interfaces and voltage domains

02
Step 2: Write The Spec

The spec IS the design file at a high level of abstraction. As you implement, you fill in real components and wiring. The file grows; the structure stays. Key principles: Good naming — name modules by their role in the system, not implementation topology (see Section 1.1). Module boundaries should encapsulate common functionality to avoid duplication at the top level. Use high-level interfaces (`ElectricPower`, `I2C`, `SPI`, `UART`, `ElectricLogic`) instead of low-level electrical connections where possible.

03
Step 3: Resolve Open Decisions

Present the user with the current architecture and any real unresolved decisions: List the modules and their responsibilities. Show the interface connections between modules. Highlight any key decisions or trade-offs made. Call out any assumptions or areas where alternatives exist.

04
Step 4: Implement Detailed Design

Now fill in the spec with real components, wiring, and constraints. This step covers package search, part selection, and detailed wiring.

05
Step 5: Build

Run builds and fix issues iteratively until everything passes. Build submodules first (if applicable) — it is much easier to get small chunks working before running the full build.

06
Step 6: Summary

Tools: Use `report_bom` for parts list and `report_variables` for constraint summary when preparing the summary. When the build finishes, give the user a summary: What was built — list the modules, key components, and interfaces. Blockers or issues — note any problems encountered and how they were resolved (or if they remain). Suggestions for next steps — what the user might want to do next (e.g., review placement, order boards, add features, run DRC).

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.