saas-study

Study a SaaS product, build evidence-first knowledge artifacts for the user's library.

When to use

• User says "study saas X", "/saas-study ", "deep-dive this SaaS", "reverse engineer this app for inspiration"
• User wants to add a SaaS to their inspiration/build library
• User asks "how does product X work mechanically?" or "what stack is this on?". First check if <library-root>/<domain>/ already has a recent study, otherwise propose running one

When NOT to use

• Replicating proprietary content
• Scraping for resale or competitive harm
• Evading bot management on hostile targets
• Endpoint fuzzing / unauth probing
• Studying sites the user has no legitimate interest in

Orchestration