@builderos/create-agent-os 0.0.2

package/src/template/agent-os/standards/global/conventions.md

@@ -0,0 +1,11 @@
+## General development conventions
+
+- **Consistent Project Structure**: Organize files and directories in a predictable, logical structure that team members can navigate easily
+- **Clear Documentation**: Maintain up-to-date README files with setup instructions, architecture overview, and contribution guidelines
+- **Version Control Best Practices**: Use clear commit messages, feature branches, and meaningful pull/merge requests with descriptions
+- **Environment Configuration**: Use environment variables for configuration; never commit secrets or API keys to version control
+- **Dependency Management**: Keep dependencies up-to-date and minimal; document why major dependencies are used
+- **Code Review Process**: Establish a consistent code review process with clear expectations for reviewers and authors
+- **Testing Requirements**: Define what level of testing is required before merging (unit tests, integration tests, etc.)
+- **Feature Flags**: Use feature flags for incomplete features rather than long-lived feature branches
+- **Changelog Maintenance**: Keep a changelog or release notes to track significant changes and improvements

package/src/template/agent-os/standards/global/error-handling.md

@@ -0,0 +1,9 @@
+## Error handling best practices
+
+- **User-Friendly Messages**: Provide clear, actionable error messages to users without exposing technical details or security information
+- **Fail Fast and Explicitly**: Validate input and check preconditions early; fail with clear error messages rather than allowing invalid state
+- **Specific Exception Types**: Use specific exception/error types rather than generic ones to enable targeted handling
+- **Centralized Error Handling**: Handle errors at appropriate boundaries (controllers, API layers) rather than scattering try-catch blocks everywhere
+- **Graceful Degradation**: Design systems to degrade gracefully when non-critical services fail rather than breaking entirely
+- **Retry Strategies**: Implement exponential backoff for transient failures in external service calls
+- **Clean Up Resources**: Always clean up resources (file handles, connections) in finally blocks or equivalent mechanisms

package/src/template/agent-os/standards/global/tech-stack.md

@@ -0,0 +1,31 @@
+## Tech stack
+
+Define your technical stack below. This serves as a reference for all team members and helps maintain consistency across the project.
+
+### Framework & Runtime
+- **Application Framework:** [e.g., Rails, Django, Next.js, Express]
+- **Language/Runtime:** [e.g., Ruby, Python, Node.js, Java]
+- **Package Manager:** [e.g., bundler, pip, npm, yarn]
+
+### Frontend
+- **JavaScript Framework:** [e.g., React, Vue, Svelte, Alpine, vanilla JS]
+- **CSS Framework:** [e.g., Tailwind CSS, Bootstrap, custom]
+- **UI Components:** [e.g., shadcn/ui, Material UI, custom library]
+
+### Database & Storage
+- **Database:** [e.g., PostgreSQL, MySQL, MongoDB]
+- **ORM/Query Builder:** [e.g., ActiveRecord, Prisma, Sequelize]
+- **Caching:** [e.g., Redis, Memcached]
+
+### Testing & Quality
+- **Test Framework:** [e.g., Jest, RSpec, pytest]
+- **Linting/Formatting:** [e.g., ESLint, Prettier, RuboCop]
+
+### Deployment & Infrastructure
+- **Hosting:** [e.g., Heroku, AWS, Vercel, Railway]
+- **CI/CD:** [e.g., GitHub Actions, CircleCI]
+
+### Third-Party Services
+- **Authentication:** [e.g., Auth0, Devise, NextAuth]
+- **Email:** [e.g., SendGrid, Postmark]
+- **Monitoring:** [e.g., Sentry, Datadog]

package/src/template/agent-os/standards/global/validation.md

@@ -0,0 +1,11 @@
+## Validation best practices
+
+- **Validate on Server Side**: Always validate on the server; never trust client-side validation alone for security or data integrity
+- **Client-Side for UX**: Use client-side validation to provide immediate user feedback, but duplicate checks server-side
+- **Fail Early**: Validate input as early as possible and reject invalid data before processing
+- **Specific Error Messages**: Provide clear, field-specific error messages that help users correct their input
+- **Allowlists Over Blocklists**: When possible, define what is allowed rather than trying to block everything that's not
+- **Type and Format Validation**: Check data types, formats, ranges, and required fields systematically
+- **Sanitize Input**: Sanitize user input to prevent injection attacks (SQL, XSS, command injection)
+- **Business Rule Validation**: Validate business rules (e.g., sufficient balance, valid dates) at the appropriate application layer
+- **Consistent Validation**: Apply validation consistently across all entry points (web forms, API endpoints, background jobs)

package/src/template/agent-os/standards/testing/test-writing.md

@@ -0,0 +1,9 @@
+## Test coverage best practices
+
+- **Write Minimal Tests During Development**: Do NOT write tests for every change or intermediate step. Focus on completing the feature implementation first, then add strategic tests only at logical completion points
+- **Test Only Core User Flows**: Write tests exclusively for critical paths and primary user workflows. Skip writing tests for non-critical utilities and secondary workflows until if/when you're instructed to do so.
+- **Defer Edge Case Testing**: Do NOT test edge cases, error states, or validation logic unless they are business-critical. These can be addressed in dedicated testing phases, not during feature development.
+- **Test Behavior, Not Implementation**: Focus tests on what the code does, not how it does it, to reduce brittleness
+- **Clear Test Names**: Use descriptive names that explain what's being tested and the expected outcome
+- **Mock External Dependencies**: Isolate units by mocking databases, APIs, file systems, and other external services
+- **Fast Execution**: Keep unit tests fast (milliseconds) so developers run them frequently during development

package/src/template/agent-os-ui/README.md

@@ -0,0 +1,73 @@
+# @antigravity/agent-os-ui
+
+The official UI capability for the **Agent OS** workflow.
+Use this library to build the control interface that guides you through the Antigravity development process (Product -> Design -> Build -> Verify).
+
+## Installation
+
+```bash
+npm install @antigravity/agent-os-ui
+```
+
+## Setup
+
+1. Import the styles:
+```ts
+import '@antigravity/agent-os-ui/style.css';
+```
+
+2. Build your Control Dashboard:
+```tsx
+import { AgentShell, GuidanceCard } from '@antigravity/agent-os-ui';
+
+export function ControlCenter() {
+  return (
+    <AgentShell sidebar={...}>
+      <div className="p-8 space-y-6">
+        {/* The core workflow component */}
+        <GuidanceCard 
+           phase="Phase 1: Strategy"
+           title="Plan Your Product"
+           description="Define your Mission and Roadmap."
+           prompt="Antigravity, plan the product..."
+        />
+      </div>
+    </AgentShell>
+  );
+}
+```
+
+## Features
+- **AgentShell**: Full application layout (Sidebar + Header + Main).
+- **AgentSidebar**: Standardized navigation menu.
+- **GuidanceCard**: The "Next Step" card with integrated prompt copying.
+- **ThemeToggle**: Dark/Light mode switcher with system sync.
+- **MarkdownViewer**: Beautifully styled Markdown rendering (Prose).
+- **StatusItem**: Standardized pills for checking system health.
+
+## Example Layout
+
+```tsx
+import { AgentShell, AgentSidebar, ThemeToggle } from '@antigravity/agent-os-ui';
+import { Home, Layers } from 'lucide-react';
+
+export default function App() {
+  return (
+    <AgentShell
+      sidebar={
+         <AgentSidebar 
+           items={[
+             { label: 'Home', icon: <Home size={18}/>, active: true },
+             { label: 'Design', icon: <Layers size={18}/> }
+           ]}
+           footer={<ThemeToggle />}
+         />
+      }
+    >
+      <div className="p-8">
+        <h1 className="text-2xl font-bold">Welcome to Agent OS</h1>
+      </div>
+    </AgentShell>
+  )
+}
+```