Skip to main content

Documentation Index

Fetch the complete documentation index at: https://archie.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Specifications is coming soon. This documentation previews what the section will look like at launch.
Editing a specification is the same as editing the blueprint: in plain language, with structural awareness, in a surface designed for non-developers. You do not write code. You write the spec.

​
Three ways to edit

Each section of a spec offers three editing modes, the same as the blueprint:
  • Direct edit — click into a screen, flow, or rule and change it inline. Useful for small tweaks, copy changes, and adding rules.
  • Spec chat — describe the change in plain language. Useful for multi-step changes (“split the orders list into two views, active and archived, and move the cancel action to the detail page”).
  • AI suggestions — Archie surfaces gaps it noticed (missing edge cases, unspecified copy, conflicting rules). You accept, modify, or dismiss each suggestion.

​
Adding constraints and rules

Validation, business rules, and edge cases live in each spec’s “Validation and edge cases” section. To add a rule:
  • Open the relevant feature’s spec
  • Click Add rule in the Validation section
  • Describe the rule in plain language: “Users can only have one active subscription at a time.” or “Orders cannot be canceled after they have shipped.”
Archie translates the rule into structured form (which field, which operator, which user type) and validates it against the rest of the spec for conflicts.

​
Refining flows

Flows are step-by-step. Each step is a user action or a system response. To refine a flow, click into it and:
  • Add a step (e.g., “show a confirmation modal before deleting”)
  • Change a step’s action (“auto-save” instead of “save when the user clicks Save”)
  • Branch a step into success and error paths
  • Add a precondition or a postcondition
If you make changes that affect the data model or user types, Archie surfaces the implications: “This requires a confirmed_at field on Orders. Add it?” You confirm and the data model updates.

​
Editing copy

Copy lives in each screen’s element list. Click any text to edit. Archie tracks copy across the project so the same string is consistent everywhere — change the cancel button’s text once and it updates in all the places it appears. For multi-locale projects, the copy view shows all locales side by side. Archie can also auto-translate when you mark a string ready for localization.

​
Marking edge cases

Edge cases are first-class in specifications. Click Add edge case in any feature’s spec to describe one in plain language: “What happens when the user disconnects mid-checkout?” Archie suggests handling — show a recovery prompt, save progress, retry on reconnect — and adds the appropriate flow steps. For complex edge cases, mark them as needs review and a human teammate can sign off before the spec drives code generation.

​
Versioning

Specifications are versioned automatically. Every edit creates a checkpoint. The version history shows what changed, when, and by whom. Roll back to any previous version from the version panel. See Specifications and code generation for how spec versions interact with code generation.