[Integration] skene-growth: An "Automated Product Manager" CLI to ground Cursor's Composer

Showcase Built for Cursor
, ,
1

I built an external CLI tool that integrates with your Cursor workflow to fix the “Empty Context” problem when starting new features. It scans your codebase and generates a manifest.json that acts as the ultimate context file for Composer.

Type: External Integration / Context Generator Repo: https://github.com/SkeneTechnologies/skene-growth

:rocket: What it does

It scans your repo to detect your Tech Stack, Database Schema, and missing Growth Features (like invite loops, billing webhooks, etc.).

It generates a structured manifest that you can feed into Cursor so the AI understands your entire architecture instantly, rather than hallucinating files that don’t exist.

:hammer_and_wrench: Setup & Usage

1. Run the Tool (Zero Install) Run this in your project root to generate the context file:

Bash

uvx skene-growth analyze . --api-key "your-key"

(This creates a manifest.json file in your root)

2. The Integration (Cursor Rule) To make this powerful, add this to your .cursorrules file so Cursor always knows to check the manifest:

Markdown

# .cursorrules

ALWAYS_CHECK:
  - Before suggesting architectural changes or new features, read 'manifest.json' (if present) to understand the existing Tech Stack and Growth Loops.
  - Use the "missing_features" section in the manifest to prioritize suggestions.

:brain: Why use this integration?

  • Stops Hallucinations: Cursor won’t suggest “adding Supabase” if the manifest proves you are already using Firebase.

  • Strategic Prompts: Instead of just writing code, Composer can now say: “I see from the manifest that you are missing a ‘Resurrection Loop’ for churned users. Shall we build that?”

Let me know if you try this workflow! It’s open source (MIT).