75+ skills. 38 agents. 35+ commands.How do you make that feel simple?
The ACOS page must communicate massive capability without overwhelming new visitors. Three design concepts explore different information architecture approaches.
Command Center
Terminal-first interface that speaks to developers
Design Approach
Leans into the CLI nature of ACOS. The page itself becomes a live terminal where visitors can search skills, browse agents, and see the command in action. Familiar to technical users, instantly communicates 'this is a real tool.'
Active Agents
75+
Skills Loaded
38
Agents Ready
< 2s
Avg Response
Strengths
- Immediate credibility with technical audience
- Interactive — visitors can search skills right on the page
- Communicates depth without long feature lists
- The terminal aesthetic matches the product reality
Trade-offs
- May feel intimidating to non-technical visitors
- Terminal metaphor limits creative layout options
- Requires JavaScript for the interactive search
Skill Galaxy
Visual constellation mapping the ACOS ecosystem
Design Approach
Represents the skill library as an interactive constellation. Each node is a category, sized by skill count, connected by relationship lines. Hovering reveals individual skills. Makes the scale tangible and explorable.
/acos
Frontend
Backend
AI/ML
DevOps
Content
Design
Security
Music
Data
Strengths
- Visceral sense of scale — you can see 75+ skills
- Exploration-driven: rewards curiosity
- Unique visual identity that stands out
- Natural grouping communicates organization
Trade-offs
- SVG-heavy — performance on low-end devices
- Accessibility challenge for screen readers
- Hover-dependent interactions need touch alternatives
Flow Architecture
Pipeline view showing how ACOS actually works
Design Approach
Instead of listing features, shows the actual flow: Input → Router → Skills → Execute → Output. Each step is a real example. Visitors understand not just what ACOS has, but how it works end-to-end.
Input
User types a command or describes intent
/acos "write a blog post about RAG"Router
Smart router classifies intent and selects agent
Intent: content → Agent: Content EngineSkills
Relevant skills auto-activate from the library
seo-content-writer + schema-markup + blog-templatesExecute
Agent works with tools: MCP servers, file system, web
Research → Outline → Draft → SEO → PublishOutput
Artifact delivered: article, code, music, deployment
Published: /blog/rag-production-patterns45s
Avg pipeline time
3-8
Skills per request
94%
Success rate
Strengths
- Tells a story — visitors understand the journey
- Real examples make abstract concepts concrete
- Linear flow is universally understandable
- Pairs well with case studies and testimonials
Trade-offs
- Less visual impact than galaxy view
- Harder to communicate the full breadth of skills
- Risk of feeling too much like documentation
Comparison
| Dimension | Command Center | Skill Galaxy | Flow Architecture |
|---|---|---|---|
| Technical audience | 10/10 | 7/10 | 8/10 |
| Non-technical appeal | 5/10 | 8/10 | 9/10 |
| Visual impact | 7/10 | 10/10 | 6/10 |
| Information density | 9/10 | 7/10 | 8/10 |
| Accessibility | 8/10 | 5/10 | 9/10 |
| Performance | 9/10 | 6/10 | 10/10 |
| Mobile experience | 7/10 | 5/10 | 9/10 |
These are live explorations. The final ACOS page may combine elements from multiple concepts.