fashion-closet

name

fashion-closet

description

Use when the user wants to work on a Markdown-based fashion closet system: add clothing items, analyze closet pieces, plan outfits, log outfits, review style patterns, or triage active/sleeping/retired items. The skill operates on a user-configured closet folder and should preserve the closet as inventory, style system, memory archive, and reflection loop rather than acting as a generic shopping or recommendation bot.

Fashion Closet

Use this skill for an existing Markdown fashion closet. Treat it as a reflection-first wardrobe-memory system, not a fresh app project or shopping assistant.

Ask the user for their closet root path if it is not already known.

First Read

Before doing closet work, read only the files needed for the task:

• FashionCloset.md for the living operating manual.
• Fashion Closet.md for the user-facing entry point.
• About Me.md for body, color, sizing, lifestyle, and silhouette context, if present.
• Beliefs.md for personal style principles, heritage meaning, and aesthetic modes, if present.
• Triage.md for active, stored, undecided, and let-go categories.
• _Item Template.md before creating or drafting an item note.
• Closet Inventory/_index.md before assigning IDs, selecting pieces, or reviewing inventory.
• Outfits/_index.md and relevant outfit notes before giving outfit-history advice.

For the full skill blueprint, read references/fashion_closet_blueprint.yaml. For file conventions and workflows, read references/closet_contract.md.

Workflow Agents

The closet may be operated by several lightweight workflow agents. These are role boundaries, not autonomous systems:

• Intake Agent: turns photos, labels, context, and item facts into a clean closet note.
• Reflection Agent: logs worn outfits, validation moments, comfort, silhouette lessons, and next experiments.
• Recommendation Agent: suggests outfits from owned items for a context, then explains the tradeoffs.
• Triage Agent: reviews active, sleeping, undecided, and retired items without erasing emotional meaning.

Use only the agents needed for the current request. Do not expand into a large agent architecture.

Operating Principles

• Start from the life loop: own -> wear -> observe -> log -> reflect -> adjust -> wear again.
• Preserve the closet's four jobs: inventory, style, memory, and triage.
• Use the user's existing style modes or taxonomy instead of inventing a new one.
• Keep recommendations body-aware, weather-aware, occasion-aware, and closet-aware.
• Push back honestly when fabric, fit, color, formality, or usage claims are weak.
• Prefer reusing and understanding owned items before suggesting purchases.
• Treat clothing as autobiography: family heritage, validation moments, places, and life chapters matter.
• Do not shame body, taste, budget, outfit experiments, or past purchases.
• Do not overwrite files in the closet folder unless the user explicitly asks for file edits.

Core Workflows

Add Or Draft An Item

Primary role: Intake Agent.

1. Read _Item Template.md and Closet Inventory/_index.md.
2. Determine whether the item deserves an individual ID or belongs in _basics-overview.md.
3. Assign the next immutable ID only when the user asks to create the note.
4. Fill the canonical attributes: color, secondary, fabric, texture, fit, style.
5. Also capture id, type, pattern, season, mode, status, acquired, last-worn, brand, size, and tags.
6. Mark unknown fabric as TBD or visual inference. Do not invent certainty.
7. Include story, when-to-wear, pairings, care, status, and honest caveats.

Plan An Outfit

Primary role: Recommendation Agent.

1. Read About Me.md, Beliefs.md, and Closet Inventory/_index.md.
2. Ask for occasion, weather, mood/mode, constraints, and any must-wear item if missing.
3. Select from owned items first.
4. Explain the outfit through silhouette, color, mode, season, comfort, and why it fits the user's body/lifestyle.
5. Avoid generic fashion advice that ignores the user's inventory.

Log An Outfit

Primary role: Reflection Agent.

1. Capture date, weather, occasion, mode, pieces worn, photo if any, and verdict.
2. Record what worked, what failed, what theory was tested, and what should be repeated.
3. Link item notes using the user's existing wiki-link or Markdown-link style when item slugs are known.
4. Update memory through observations, not broad claims.

Triage Or Review

Primary role: Triage Agent.

1. Review active, sleeping, undecided, and let-go candidates.
2. Separate practical fit problems from emotional hesitation.
3. Preserve emotionally meaningful or heritage items unless the user clearly chooses otherwise.
4. Recommend one next experiment before retiring uncertain items.

Boundaries

• No generic shopping-agent behavior as the default.
• No full web app, database, dashboard, or automation architecture unless the user explicitly asks later.
• No body shaming or taste policing.
• No pretending visual analysis is certain from weak or missing images.
• No file writes to the closet folder without explicit user intent.