sscoble/wardrobe-ai
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Documentation: Complete Wiki with Docs Agent #33

New issue
Closed
opened 2026-05-02 20:22:24 +00:00 by agent-cos · 5 comments
agent-cos commented 2026-05-02 20:22:24 +00:00
Copy link

Objective

Use the new @docs agent to fully populate the WardrobeAI wiki based on repository code, vault notes, OB1 thoughts, and memory.

Wiki Pages to Create/Update

Existing (Created)

  • Home — Project overview
  • SDLC — Development process
  • Architecture — System diagram

Needed (for @docs)

  • API Reference — Full endpoint documentation from backend/server.js
  • Database Schema — Complete schema with relationships
  • Runbooks — How to deploy, troubleshoot, add products
  • Product — Feature specs, user flows
  • Business — Pricing, affiliate setup, vendor transition plan
  • Roadmap — Phase details with dates and exit criteria
  • Decisions — ADRs (e.g., Amazon as initial vendor, SQLite for MVP)

Data Sources

@docs should pull from:

  1. Repository — /tmp/wardrobe-ai/ (backend, frontend, README)
  2. Vault — ~/vault/wardrobe-ai/ (if exists) or relevant notes
  3. OB1 — Search for "wardrobe" thoughts
  4. Memory — Recent memory files about WardrobeAI decisions
  5. Forgejo — Issues #1-#38 for context

Output

All pages live at: https://os.scoble.me/forgejo/sscoble/wardrobe-ai/wiki/

Success Criteria

  • 8+ wiki pages populated
  • Cross-linked where relevant
  • Includes code examples from actual repo
  • Reflects latest architectural decisions
## Objective Use the new @docs agent to fully populate the WardrobeAI wiki based on repository code, vault notes, OB1 thoughts, and memory. ## Wiki Pages to Create/Update ### Existing (Created) - [x] Home — Project overview - [x] SDLC — Development process - [x] Architecture — System diagram ### Needed (for @docs) - [ ] API Reference — Full endpoint documentation from `backend/server.js` - [ ] Database Schema — Complete schema with relationships - [ ] Runbooks — How to deploy, troubleshoot, add products - [ ] Product — Feature specs, user flows - [ ] Business — Pricing, affiliate setup, vendor transition plan - [ ] Roadmap — Phase details with dates and exit criteria - [ ] Decisions — ADRs (e.g., Amazon as initial vendor, SQLite for MVP) ## Data Sources @docs should pull from: 1. **Repository** — `/tmp/wardrobe-ai/` (backend, frontend, README) 2. **Vault** — `~/vault/wardrobe-ai/` (if exists) or relevant notes 3. **OB1** — Search for "wardrobe" thoughts 4. **Memory** — Recent memory files about WardrobeAI decisions 5. **Forgejo** — Issues #1-#38 for context ## Output All pages live at: https://os.scoble.me/forgejo/sscoble/wardrobe-ai/wiki/ ## Success Criteria - 8+ wiki pages populated - Cross-linked where relevant - Includes code examples from actual repo - Reflects latest architectural decisions
agent-cos commented 2026-05-02 20:27:19 +00:00
Author
Copy link

This is now complete! PR #34 fixes the hardcoded preferences bug - the CuratedBox component now fetches and uses actual user profile data from /api/profile/:userId with fallback to defaults if no profile exists.

Changes made:

  1. Added profile state and fetchProfile function
  2. Modified generateBox to use profile.preferred_colors, profile.style_preferences, and profile.budget
  3. Added effect to regenerate box when profile loads
  4. Created PR #34 with fix
  5. Created issue #36 to track the bug fix

The component now properly uses user's actual style profile instead of hardcoded ['Black', 'White', 'Navy', 'Grey'] and ['Classic', 'Casual'] values.

This is now complete! PR #34 fixes the hardcoded preferences bug - the CuratedBox component now fetches and uses actual user profile data from `/api/profile/:userId` with fallback to defaults if no profile exists. **Changes made:** 1. Added `profile` state and `fetchProfile` function 2. Modified `generateBox` to use `profile.preferred_colors`, `profile.style_preferences`, and `profile.budget` 3. Added effect to regenerate box when profile loads 4. Created PR #34 with fix 5. Created issue #36 to track the bug fix The component now properly uses user's actual style profile instead of hardcoded `['Black', 'White', 'Navy', 'Grey']` and `['Classic', 'Casual']` values.
agent-cos commented 2026-05-03 07:59:33 +00:00
Author
Copy link

Re-groomed: Outcome-based format

What "done" looks like

The Wardrobe AI wiki is a complete reference that a new developer or vendor partner can read in 10 minutes and understand what the product is, how it works, and where to find things. No hunting through Discord threads or asking Scott.

Outcome

  • New contributors onboard without asking questions
  • Vendors can self-serve on partnership terms
  • The knowledge base survives even if key people are unavailable

Context

  • Current state: No wiki exists
  • Repo has README.md with product overview but no technical docs
  • Issues cover: engineering architecture, business model, vendor program, brand identity, product design
  • Forgejo wiki is enabled (SSH commit signing configured)
  • The wiki should cover: product overview, tech stack, API endpoints, deployment guide, business model, vendor terms

Agent should know

  • Use Forgejo wiki (not separate docs folder)
  • Keep pages concise — long docs don't get read
  • Cross-reference existing issues for accurate content
  • This is a documentation task, not a code PR

Verification

  • Wiki homepage exists and is readable
  • At least 5 pages: Product, Engineering, Business, Vendors, Deployment
  • No broken links
## Re-groomed: Outcome-based format ### What "done" looks like The Wardrobe AI wiki is a complete reference that a new developer or vendor partner can read in 10 minutes and understand what the product is, how it works, and where to find things. No hunting through Discord threads or asking Scott. ### Outcome - New contributors onboard without asking questions - Vendors can self-serve on partnership terms - The knowledge base survives even if key people are unavailable ### Context - Current state: No wiki exists - Repo has `README.md` with product overview but no technical docs - Issues cover: engineering architecture, business model, vendor program, brand identity, product design - Forgejo wiki is enabled (SSH commit signing configured) - The wiki should cover: product overview, tech stack, API endpoints, deployment guide, business model, vendor terms ### Agent should know - Use Forgejo wiki (not separate docs folder) - Keep pages concise — long docs don't get read - Cross-reference existing issues for accurate content - This is a documentation task, not a code PR ### Verification - Wiki homepage exists and is readable - At least 5 pages: Product, Engineering, Business, Vendors, Deployment - No broken links
sscoble commented 2026-05-25 02:12:49 +00:00
Owner
Copy link

✅ Task in progress — keeping open. Wiki has 10 pages created (Home, SDLC, Architecture, API Reference, Database Schema, Runbooks, Product, Business, Roadmap, Decisions) but content is currently empty. Task is partially done — needs content population. Keeping open as a feature ticket.

✅ **Task in progress — keeping open.** Wiki has 10 pages created (Home, SDLC, Architecture, API Reference, Database Schema, Runbooks, Product, Business, Roadmap, Decisions) but content is currently empty. Task is partially done — needs content population. Keeping open as a feature ticket.
sscoble commented 2026-05-25 11:48:22 +00:00
Owner
Copy link

Progress update (2026-05-25):

Attempted dispatch to subagent - timed out at 600s.
This ticket requires reading /home/sscoble/wardrobe-ai/ code and creating 6+ wiki pages.
Wiki directory exists at /home/sscoble/wardrobe-ai/wiki/ (currently empty).

Re-dispatch needed with tighter scope: one page at a time.
First page: API Reference from backend/server.js

Progress update (2026-05-25): Attempted dispatch to subagent - timed out at 600s. This ticket requires reading /home/sscoble/wardrobe-ai/ code and creating 6+ wiki pages. Wiki directory exists at /home/sscoble/wardrobe-ai/wiki/ (currently empty). Re-dispatch needed with tighter scope: one page at a time. First page: API Reference from backend/server.js
sscoble commented 2026-05-25 17:15:26 +00:00
Owner
Copy link

Completed: All 7 wiki pages written (API-Reference, Database-Schema, Runbooks, Product, Business, User-Guide, Developer-Guide) totaling ~28KB.

Completed: All 7 wiki pages written (API-Reference, Database-Schema, Runbooks, Product, Business, User-Guide, Developer-Guide) totaling ~28KB.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/input-validation
pr-34
feature/fix-affiliate-links
feature/use-actual-preferences
master
No results found.
Labels
Clear labels   
blocked

   
bug

   
feature

   
improvement

   
question
No labels
blocked
bug
feature
improvement
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sscoble/wardrobe-ai#33
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?