Detects product type from user requirements to trigger domain-specific architecture depth sections
Analyzes project requirements to detect product types and trigger domain-specific architecture sections.
npx claudepluginhub navraj007in/architecture-cowork-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
templates/ai-agent.mdtemplates/content-platform.mdtemplates/ecommerce-marketplace.mdtemplates/file-upload-storage.mdtemplates/multi-tenant-saas.mdtemplates/real-time-collaboration.mdPurpose: 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
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.