claudex-setup 0.2.0 → 0.2.1

package/APF.md

@@ -1,121 +0,0 @@
-# CLAUDEX-SETUP: Autonomous Project Framework
-
-## Project Definition
-
-**Product:** `claudex-setup` - CLI tool that audits and optimizes any project for Claude Code
-**Revenue model:** Free CLI (audience) + Premium newsletter (revenue) + Consulting (high-ticket)
-**Unfair advantage:** 972 verified techniques, 773 tested. Nobody else has this.
-
----
-
-## Phase 0: Launch Parameters
-
-- **Budget:** $0 initial (Claude Max already active, n8n running)
-- **Revenue target:** First $100 within 30 days
-- **Timeline:** MVP in 1 week, launch in 2 weeks
-- **Human provides:** npm account, GitHub repo, social media publish (or n8n automation)
-- **Claude handles:** Everything else
-
----
-
-## Strategy: 3-Layer Revenue
-
-### Layer 1: Free CLI (Audience Builder)
-```
-npx claudex-setup → audit + setup your project for Claude Code
-```
-- Free, open source, zero friction
-- Goal: 1,000 downloads in first month
-- Converts to newsletter subscribers
-
-### Layer 2: Newsletter / Content (Recurring Revenue)
-```
-"Claude Code Weekly" - 5 techniques you missed this week
-```
-- Free tier: weekly email with 3 tips
-- Premium: daily tips + full technique database access ($10/month)
-- Source: 972 items = 2+ years of unique daily content
-
-### Layer 3: One-time Products (Cash Injection)
-```
-"The Claude Code Playbook" - complete guide, $29
-```
-- PDF/Notion guide built from catalog + by-usecase.md
-- Upsell from free CLI users
-- Zero marginal cost
-
----
-
-## Build Plan (Priority Order)
-
-### Week 1: CLI MVP + GitHub
-- [ ] Build `claudex-setup` CLI (audit + setup)
-- [ ] Publish to npm
-- [ ] GitHub repo with good README
-- [ ] Test on 3 real projects
-
-### Week 2: Landing Page + Content Pipeline
-- [ ] Landing page (Vercel, free)
-- [ ] Newsletter setup (Buttondown free tier or similar)
-- [ ] Write first 10 newsletter issues from catalog
-- [ ] n8n automation: scheduled content publishing
-
-### Week 3: Launch
-- [ ] Post on Reddit r/ClaudeAI, r/ChatGPTPro
-- [ ] Post on Hacker News (Show HN)
-- [ ] Post on Dev.to, Medium
-- [ ] GitHub: add to awesome-claude-code lists
-- [ ] Product Hunt launch
-
-### Week 4: Measure + Iterate
-- [ ] Track: downloads, stars, subscribers, revenue
-- [ ] Analyze: which techniques get most engagement
-- [ ] Decide: continue / pivot / expand
-
----
-
-## What I Need From You
-
-### One-time setup (5 minutes total):
-1. **npm account** - create at npmjs.com if don't have, give me auth token
-2. **GitHub** - create repo `claudex-setup` (or I use existing account)
-3. **Social media** - either:
-   - Give me access to post (Twitter/X, Reddit)
-   - OR: I prepare posts, n8n publishes automatically
-   - OR: I prepare posts, you copy-paste once a day (1 min)
-
-### When I ask for budget approval:
-- Domain (~$12) - optional, can start with github.io
-- Newsletter service - free tier available
-- Everything else: $0
-
----
-
-## Success Metrics
-
-| Metric | Week 1 | Week 2 | Week 4 | Month 2 | Pivot if below |
-|--------|--------|--------|--------|---------|---------------|
-| npm downloads | 50 | 200 | 500 | 2,000 | <100 at week 4 |
-| GitHub stars | 10 | 30 | 100 | 300 | <20 at week 4 |
-| Newsletter subs | 0 | 20 | 100 | 300 | <30 at week 4 |
-| Revenue | $0 | $0 | $50 | $500 | <$50 at month 2 |
-
-## Stop Criteria
-- Week 4: <100 downloads AND <20 stars → pivot approach
-- Month 2: <$50 revenue → reassess product-market fit
-- Month 3: <$200 revenue → stop or major pivot
-
-## Continue Criteria
-- Week 4: 500+ downloads → accelerate content
-- Month 2: $200+ revenue → invest in premium features
-- Month 3: $1,000+ revenue → dedicated infrastructure
-
----
-
-## Decision Log
-
-| Date | Decision | Reasoning |
-|------|----------|-----------|
-| 2026-03-30 | Start with CLI + newsletter model | Lowest cost, fastest to market, leverages existing 972 items |
-| 2026-03-30 | Free CLI, premium content | CLI builds audience, content monetizes. Proven model. |
-| 2026-03-30 | n8n for automation | Already running on Docker, zero additional cost |

package/CLAUDE.md

@@ -1,42 +0,0 @@
-# CLAUDEX-SETUP — Autonomous Product Project
-
-## On Every Session Start
-1. Read `apf/state.json` for current metrics
-2. Read `apf/todo.md` for pending tasks
-3. Check metrics:
-   - npm: `curl -s "https://api.npmjs.org/downloads/point/last-week/claudex-setup"`
-   - GitHub: `curl -s https://api.github.com/repos/DnaFin/claudex`
-   - Dev.to: `curl -s -H "api-key: RZ8Zgf5GUcc6dVNErSiwocYu" https://dev.to/api/articles/me?per_page=5`
-4. Update `apf/state.json`
-5. Execute highest priority from `apf/todo.md`
-6. Before ending: update todo.md + state.json + commit + push
-
-## Credentials (.env)
-- npm: NPM_TOKEN
-- GitHub: GITHUB_TOKEN (DnaFin)
-- Dev.to: DEVTO_API_KEY
-- n8n: N8N_API_KEY (localhost:5678)
-
-## Decision Authority
-I decide everything autonomously. Ask human ONLY for:
-- Budget approval (any spend > $0)
-- New account credentials
-- Captcha / manual verification
-
-## Architecture
-```mermaid
-graph TD
-    CLAUDEX[CLAUDEX Research 1107 items] -->|knowledge| CLI[CLI Tool npx claudex-setup]
-    CLI -->|downloads| NPM[npm registry]
-    CLI -->|code| GH[GitHub DnaFin/claudex]
-    GH -->|hosting| LP[Landing Page]
-    CLAUDEX -->|content| DT[Dev.to Articles]
-    DT -->|traffic| GH
-    N8N[n8n Weekly Publisher] -->|auto-post| DT
-    Users -->|feedback| CLI
-    Users -->|feedback| CLAUDEX
-```
-
-## Language
-- Code: English
-- User communication: Hebrew

package/CONTRIBUTING.md

@@ -1,53 +0,0 @@
-# Contributing to claudex-setup
-
-## Adding a New Check
-
-1. Open `src/techniques.js`
-2. Add an entry to the `CHECKS` array:
-   ```js
-   { id: 'my-check', category: 'Quality', weight: 10, label: 'Description',
-     test: (ctx) => fs.existsSync(path.join(ctx.root, 'some-file')),
-     fix: 'Add some-file to your project root.' }
-   ```
-3. The `test` function receives a context object with `root`, `stack`, and `files`
-4. Run `npm test` to verify
-
-## Adding a New Template
-
-1. Open `src/setup.js`
-2. Add a template function to `TEMPLATES`:
-   ```js
-   TEMPLATES['my-template'] = (ctx) => `file content for ${ctx.stack}`;
-   ```
-3. Register it in the `generateFiles()` function with its output path
-4. Templates receive the same context object as checks
-
-## Adding a New Stack
-
-1. Open `src/techniques.js`
-2. Add an entry to the `STACKS` object:
-   ```js
-   STACKS['my-framework'] = {
-     detect: (ctx) => ctx.files.includes('my-framework.config.js'),
-     label: 'My Framework',
-     testCmd: 'my-framework test',
-     lintCmd: 'my-framework lint'
-   };
-   ```
-3. Stack detection runs before checks, so checks can reference `ctx.stack`
-
-## Research Backing
-
-Every check should trace back to a technique in the [CLAUDEX catalog](https://github.com/DnaFin/claudex). When adding checks, reference the technique ID in a comment:
-
-```js
-// CLAUDEX: T-042 (Mermaid diagrams reduce token usage by 73%)
-```
-
-## Running Tests
-
-```bash
-npm test
-```
-
-Tests run all checks against fixture projects in `test/fixtures/`.

package/apf/state.json

@@ -1,29 +0,0 @@
-{
-  "project": "claudex-setup",
-  "launched": "2026-03-30",
-  "version": "0.1.0",
-  "metrics": {
-    "npm_downloads_total": 0,
-    "github_stars": 0,
-    "devto_views": 0,
-    "devto_reactions": 0,
-    "newsletter_subs": 0,
-    "revenue": 0
-  },
-  "platforms": {
-    "npm": "live",
-    "github": "live",
-    "devto": "live",
-    "landing_page": "live",
-    "n8n_workflow": "active",
-    "reddit": "pending_api_approval",
-    "hackernews": "pending_account_maturity"
-  },
-  "content": {
-    "devto_articles_published": 1,
-    "reddit_posts": 1,
-    "launch_posts_ready": 5
-  },
-  "last_session": "2026-03-30",
-  "sessions_total": 1
-}

package/apf/todo.md

@@ -1,40 +0,0 @@
-# Task Queue — CLAUDEX-SETUP
-
-## Priority 1 (Next Session)
-- [ ] Measure: npm downloads, GitHub stars, Dev.to article views
-- [ ] Write Dev.to article #2: "5 CLAUDE.md mistakes killing your Claude Code productivity"
-- [ ] Improve CLI: add more technique checks (currently 12, target 25)
-- [ ] Try Reddit again (comment on existing posts to build karma first)
-- [ ] Check if awesome-claude-code PR/issue got response
-
-## Priority 2 (This Week)
-- [ ] Write Dev.to article #3: "Hooks vs CLAUDE.md: Why 100% beats 80%"
-- [ ] Add `--fix` flag to audit (suggest specific fixes inline)
-- [ ] Add JSON schema validation for .claude/settings.json
-- [ ] Create newsletter signup (Buttondown free tier)
-- [ ] Try posting on r/programming (different subreddit, less strict)
-
-## Priority 3 (Week 2)
-- [ ] Premium content: "Claude Code Playbook" PDF ($29)
-- [ ] More stack-specific templates (Django, FastAPI, Rust, Go)
-- [ ] Add technique count to CLI output ("12/972 best practices checked")
-- [ ] Collect user feedback (GitHub issues, Dev.to comments)
-- [ ] Try HN again when account is mature
-
-## Priority 4 (Month 1)
-- [ ] Newsletter with 3 free tips/week from catalog
-- [ ] Premium tier: full technique database access
-- [ ] Consulting landing page
-- [ ] Cross-post content to Medium, LinkedIn
-
-## Completed
-- [x] Build CLI MVP (audit + setup)
-- [x] Publish to npm
-- [x] Create GitHub repo
-- [x] Build landing page
-- [x] Publish Dev.to article #1
-- [x] Post on Reddit r/ClaudeAI (removed by filters)
-- [x] Submit to awesome-claude-code
-- [x] Setup n8n weekly publisher
-- [x] Create publish.js automation tool
-- [x] Redesign landing page (anti-AI-slop)

package/content/devto-article.json

@@ -1,8 +0,0 @@
-{
-  "article": {
-    "title": "972 Claude Code Techniques: What I Learned Building the Most Comprehensive Catalog",
-    "published": true,
-    "tags": ["claude", "ai", "productivity", "devtools"],
-    "body_markdown": "After 39 research cycles, I cataloged **972 Claude Code techniques** and tested **773 of them with real evidence**. Here are the top 10 things most developers are missing.\n\n## The Problem\n\nClaude Code is incredibly powerful - 74 releases in 52 days, hundreds of features. But most projects barely scratch the surface.\n\nI built a CLI that scores your project:\n\n```bash\nnpx claudex-setup\n```\n\nMost projects score **10-20 out of 100**. After running setup, they jump to **70+**.\n\n## Top 10 Things You're Probably Missing\n\n### 1. CLAUDE.md (Impact: Critical)\n\nClaude reads this file at the start of every session. Without it, Claude doesn't know your build commands, code style, or project rules.\n\nRun `/init` to auto-generate one from your codebase.\n\n### 2. Mermaid Architecture Diagrams (Saves 73% Tokens)\n\nA Mermaid diagram in CLAUDE.md gives Claude your project structure in a fraction of the tokens that prose would require.\n\n### 3. Hooks > CLAUDE.md Rules (100% vs 80%)\n\nCLAUDE.md instructions are advisory (~80% compliance). Hooks are deterministic (100%). Auto-lint after every edit. Every time. No exceptions.\n\n### 4. Custom Commands\n\nStop typing the same prompts. Create `/test`, `/deploy`, `/review` in `.claude/commands/`.\n\n### 5. Verification Loops (The #1 Best Practice)\n\nClaude performs dramatically better when it can verify its own work. Include test commands in CLAUDE.md.\n\n> This is the single highest-leverage thing you can do. - Anthropic Best Practices\n\n### 6. Path-Specific Rules\n\nDifferent conventions for frontend vs backend files in `.claude/rules/`.\n\n### 7. XML Tags for Structured Prompts\n\nUse `<constraints>`, `<validation>` in CLAUDE.md for unambiguous instructions. 30% quality improvement (Anthropic-measured).\n\n### 8. Custom Agents\n\nSpecialized subagents for focused tasks: security-reviewer, test-writer in `.claude/agents/`.\n\n### 9. Skills (On-Demand Knowledge)\n\nUnlike CLAUDE.md (loaded every session), skills load only when relevant. Run `/fix-issue 1234` and Claude handles the rest.\n\n### 10. MCP Servers\n\nConnect Claude to your database, ticket system, or Slack via MCP configuration.\n\n## Try It Now\n\n```bash\nnpx claudex-setup        # Audit (10 seconds)\nnpx claudex-setup setup  # Auto-fix\n```\n\nFree, open source, zero dependencies.\n\n**GitHub:** [github.com/DnaFin/claudex](https://github.com/DnaFin/claudex)\n\n---\n\n*Built from [CLAUDEX](https://github.com/DnaFin/claudex) - 972 verified Claude Code techniques, 773 tested with real evidence.*"
-  }
-}

package/content/launch-posts.md

@@ -1,160 +0,0 @@
-# Launch Posts — Ready to Publish
-
-## Post 1: Reddit r/ClaudeAI
-
-**Title:** I built a tool that audits your project for Claude Code optimization — scores you 0-100
-
-**Body:**
-After cataloging 972 Claude Code techniques and testing 773 of them, I built a CLI that checks if your project is actually set up to get the most out of Claude Code.
-
-Most projects score around 10-20/100. After running setup, they jump to 70+.
-
-```
-npx claudex-setup
-```
-
-It checks for: CLAUDE.md, hooks, custom commands, skills, agents, Mermaid diagrams, XML tags, path rules, MCP config, permissions, and more.
-
-Then `npx claudex-setup setup` auto-creates everything that's missing, tailored to your stack (React, Python, TypeScript, etc).
-
-Zero dependencies. No API keys. Runs entirely local.
-
-GitHub: https://github.com/DnaFin/claudex
-
-Would love feedback!
-
----
-
-## Post 2: Reddit r/ChatGPTCoding
-
-**Title:** Your Claude Code project is probably running at 10% efficiency. Here's how to check.
-
-**Body:**
-I spent weeks cataloging every Claude Code feature, technique, and best practice — 972 total, 773 tested with real evidence.
-
-Turns out most projects are missing basic stuff that makes a huge difference:
-- No CLAUDE.md (Claude doesn't know your project conventions)
-- No hooks (no auto-lint, no auto-test)
-- No custom commands (repeating the same prompts manually)
-- No Mermaid diagrams (wasting 73% more tokens on prose descriptions)
-
-Built a quick checker:
-```
-npx claudex-setup
-```
-
-Scores your project 0-100, tells you exactly what to fix, and can auto-apply everything.
-
-Free, open source, zero dependencies: https://github.com/DnaFin/claudex
-
----
-
-## Post 3: Dev.to Article
-
-**Title:** 972 Claude Code Techniques: What I Learned Building the Most Comprehensive Catalog
-
-**Body (excerpt):**
-I set out to catalog every single Claude Code capability, technique, and best practice. 39 research cycles later, I have 972 items — 773 tested with real evidence.
-
-Here are the top 10 things most developers are missing:
-
-1. **CLAUDE.md** — Claude reads this at the start of every session. Without it, Claude doesn't know your build commands, code style, or project rules.
-
-2. **Mermaid diagrams** — A Mermaid architecture diagram saves 73% tokens compared to describing your project in prose.
-
-3. **Hooks** — Auto-lint after every edit. Auto-test before every commit. Hooks fire 100% of the time, CLAUDE.md rules fire ~80%.
-
-4. **Custom commands** — `/test`, `/deploy`, `/review` — package your repeated workflows.
-
-5. **Verification loops** — Tell Claude how to verify its own work. Include test commands in CLAUDE.md.
-
-6. **Path-specific rules** — Different conventions for frontend vs backend files.
-
-7. **XML tags** — `<constraints>`, `<validation>` in CLAUDE.md = unambiguous instructions.
-
-8. **Custom agents** — Security reviewer, test writer — specialized subagents for focused tasks.
-
-9. **Skills** — Domain-specific workflows that load on demand, not every session.
-
-10. **MCP servers** — Connect Claude to your database, ticket system, Slack.
-
-I packaged this into a CLI that checks your project:
-```
-npx claudex-setup
-```
-
-Full catalog: https://github.com/DnaFin/claudex
-
----
-
-## Post 4: Twitter/X Thread
-
-**Tweet 1:**
-I cataloged 972 Claude Code techniques and tested 773 of them.
-
-Most projects use less than 5% of what Claude Code can do.
-
-Here's a free tool that checks your project and tells you exactly what's missing:
-
-npx claudex-setup
-
-Thread 🧵👇
-
-**Tweet 2:**
-The #1 thing you're probably missing: CLAUDE.md
-
-It's a file Claude reads at the start of every session. Without it, Claude doesn't know your:
-- Build commands
-- Code style
-- Testing framework
-- Project architecture
-
-Takes 2 minutes to create. Impact: massive.
-
-**Tweet 3:**
-#2: Mermaid diagrams in CLAUDE.md
-
-A few hundred tokens of Mermaid syntax conveys what takes thousands of tokens in prose.
-
-73% token savings = faster responses, lower cost, better context.
-
-**Tweet 4:**
-#3: Hooks > CLAUDE.md rules
-
-CLAUDE.md instructions = ~80% compliance
-Hooks = 100% enforcement
-
-Auto-lint after edits. Block commits without tests. Prevent force-push.
-
-Hooks are deterministic. Instructions are advisory.
-
-**Tweet 5:**
-Want to check your project in 10 seconds?
-
-npx claudex-setup
-
-Scores 0-100. Shows what's missing. Auto-fixes with `setup`.
-
-Free. Open source. Zero dependencies.
-
-https://github.com/DnaFin/claudex
-
----
-
-## Post 5: Hacker News (Show HN)
-
-**Title:** Show HN: claudex-setup – Audit any project for Claude Code optimization (972 techniques)
-
-**Body:**
-I built a CLI tool that scores your project against Claude Code best practices.
-
-After researching 972 techniques (773 tested live), most projects score 10-20 out of 100 because they're missing basic optimizations like CLAUDE.md files, hooks, custom commands, and architecture diagrams.
-
-npx claudex-setup → audit (0-100 score)
-npx claudex-setup setup → auto-fix
-
-Detects your stack (React, Python, TS, Rust, Go, etc) and tailors recommendations.
-
-Zero dependencies, no API keys, runs locally.
-
-https://github.com/DnaFin/claudex