skills/product-type-detector/SKILL.md
Detects product type from user requirements to trigger domain-specific architecture depth sections
npx skillsauth add navraj007in/architecture-cowork-plugin product-type-detectorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Purpose: Automatically identifies the product type(s) from user requirements to trigger appropriate domain-specific architecture depth sections.
When to Use: Internally by architecture-methodology skill during blueprint generation. Never invoke directly.
Analyze the user's requirements and detect ALL applicable product types. A single product can match multiple types.
Triggers:
Detection Logic:
IF (mentions "real-time" OR "live" OR "chat" OR "messaging" OR "collaboration")
AND (mentions "users see updates immediately" OR "WebSocket" OR "presence" OR "typing indicator")
THEN product_type.includes("real-time-collaboration")
Depth Sections to Add:
Triggers:
Detection Logic:
IF (mentions "multi-tenant" OR "workspace" OR "each company" OR "B2B" OR "organization")
OR (mentions "SSO" OR "SAML" OR "custom domain per customer" OR "white-label")
THEN product_type.includes("multi-tenant-saas")
Depth Sections to Add:
Triggers:
Detection Logic:
IF (mentions "file upload" OR "file sharing" OR "document" OR "media" OR "attachment" OR "storage")
AND (mentions "users can upload" OR "file management" OR "asset library")
THEN product_type.includes("file-upload-storage")
Depth Sections to Add:
Triggers:
Detection Logic:
IF (mentions "e-commerce" OR "marketplace" OR "shopping" OR "cart" OR "checkout" OR "payment" OR "stripe")
OR (mentions "products" AND "buy" AND "sell")
THEN product_type.includes("ecommerce-marketplace")
Depth Sections to Add:
Triggers:
Detection Logic:
IF (mentions "AI" OR "LLM" OR "agent" OR "Claude" OR "GPT" OR "chatbot")
AND (mentions "tool calling" OR "function calling" OR "RAG" OR "embeddings" OR "knowledge base")
THEN product_type.includes("ai-agent")
Depth Sections to Add:
Triggers:
Detection Logic:
IF (mentions "blog" OR "CMS" OR "publishing" OR "posts" OR "articles" OR "content")
AND (mentions "SEO" OR "rich text" OR "editor" OR "publishing workflow")
THEN product_type.includes("content-platform")
Depth Sections to Add:
Return detected product types as array:
{
"product_types": [
"real-time-collaboration",
"multi-tenant-saas"
],
"confidence": {
"real-time-collaboration": "high",
"multi-tenant-saas": "medium"
},
"reasoning": {
"real-time-collaboration": "User mentioned 'real-time chat' and 'WebSocket' explicitly",
"multi-tenant-saas": "Mentioned 'workspace' and 'each company gets their own account'"
}
}
Input:
User: "Build a team collaboration tool like Slack. Each company gets their own workspace with channels and DMs. Real-time messaging with typing indicators. File sharing. 100 companies, 10-50 users each."
Output:
{
"product_types": [
"real-time-collaboration",
"multi-tenant-saas",
"file-upload-storage"
],
"confidence": {
"real-time-collaboration": "high",
"multi-tenant-saas": "high",
"file-upload-storage": "medium"
},
"reasoning": {
"real-time-collaboration": "Explicitly mentions 'real-time messaging' and 'typing indicators'",
"multi-tenant-saas": "Each company gets workspace (multi-tenant pattern)",
"file-upload-storage": "Includes file sharing feature"
}
}
The architecture-methodology skill will:
Example Flow:
User submits requirements
↓
Architecture methodology gathers info via Essential Questions
↓
Product type detector analyzes requirements
↓
Detector returns: ["real-time-collaboration", "multi-tenant-saas"]
↓
Architecture methodology injects:
- Message Delivery Model section (real-time)
- Tenant Isolation Design section (multi-tenant)
↓
Blueprint generated with domain-specific depth
Case 1: No product type detected
Case 2: Multiple product types detected
Case 3: Conflicting depth sections
development
# Trade-Off Analysis Skill Quantifies exact trade-offs when switching between architecture options. Shows users precisely what they gain and lose when choosing Option A over Option B. ## When to Use Use this skill to help users decide between options by showing: 1. **Cost difference** — how much more/less per month? 2. **Performance difference** — how much faster/slower? 3. **Complexity difference** — how much harder to build/maintain? 4. **Scalability difference** — when does this option hit
testing
# Stage Detection Skill Detects the current project stage (concept → mvp → growth → enterprise) based on `_state.json` field presence and completeness. Used by `/architect:next-steps`, `/architect:check-state`, and roadmap commands. ## When to Use Invoke this skill when you need to determine what stage a project is at based on its state file. Stage detection drives: - Command recommendations (what to run next) - Required fields validation (what should exist at this stage) - Risk assessment (w
development
# Stack Swap Simulator Skill Estimates cost and effort to switch from one tech stack to another. Helps answer: "Can we migrate later if needed?" ## When to Use Use this skill to understand: 1. **Cost of switching stacks** — engineer weeks + downtime risk 2. **Timeline to switch** — how long is the project? 3. **Risk of switching** — what can go wrong? 4. **ROI of switching** — does it save money long-term? 5. **Backwards compatibility** — can we do a gradual migration? ## Input Provide sour
tools
# Stack Compatibility Skill Verifies that chosen technologies integrate well together. Prevents "I picked these tools and they don't work well together" regrets. ## When to Use Use this skill to verify: 1. **Chosen tools work together** — React + Node + MongoDB = good? 2. **No hidden incompatibilities** — will I hit issues in production? 3. **Team can support it** — do we have expertise for this combo? 4. **Licenses compatible** — can we use these together commercially? 5. **Performance assum