Skillget

claude-code-kit

workflow
Security Audit
Warn
Health Warn
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Warn
  • Code scan incomplete — No supported source files were scanned during light audit
Permissions Pass
  • Permissions — No dangerous permissions requested
Purpose
This project provides a documented workflow and a collection of CLAUDE.md templates designed for production-level development using Claude Code. It focuses on cross-repo memory, deployment verification, and Southeast Asian operational patterns tailored for solo founders.

Security Assessment
The overall risk is rated as Low. The automated audit confirms that no dangerous permissions are requested. Because this is primarily a methodology and documentation repository rather than executable software, the source code scan was incomplete, which is expected. The templates and suggested workflows rely on local shell execution (such as build commands and curl requests for deployment verification) but do not appear to access sensitive user data or make unauthorized network requests. No hardcoded secrets were detected.

Quality Assessment
The repository is actively maintained, with its most recent push occurring today. It is fully licensed under the permissive and standard MIT license. However, it has extremely low visibility within the broader developer community, currently sitting at only 5 GitHub stars. This indicates a small user base and means it has not been widely peer-reviewed, which slightly lowers the community trust level.

Verdict
Safe to use. It is essentially a helpful collection of Markdown documentation and templates, carrying virtually no inherent security risks for developers looking to adopt its workflow patterns.
SUMMARY

Documented workflow + CLAUDE.md templates for production Claude Code development. Indonesian dev community-first.

README.md

Claude Code Kit

Opinionated methodology for solo founders shipping multiple ventures with Claude Code.

The boring infrastructure part. The bit that doesn't make YouTube thumbnails but actually makes you money.

Start here

First time? Open this repo in Claude Code (cd claude-code-kit && claude) and just say "halo" or "hi" — Claude will detect your situation and route you to the right next step. The kit teaches Claude Code patterns by USING them.

Just want to read? Start with docs/01-claude-md-rules.md — the actual CLAUDE.md ruleset running across 8 production repositories. Begins from "what rules do you actually put in CLAUDE.md?"

Claude misbehaves in your existing repo? docs/02-fixing-broken-claude-md.md — 6 common failure modes + fixes.

Want production-discipline skills? See skills/INDEX.md — 7 reusable Claude Code skills (security audits, SEO audits, pre-deploy 3-gate verification, secret rotation walkthrough, voice register check).

Want to contribute? See CONTRIBUTING.md.

What this is

Methodology + templates + tooling extracted from running 8+ active ventures under one holding (PT Adikarya Wisata Indah Nesia) with Claude Code as the primary development partner. SEA payment realities, Indonesian dev voice, cross-repo memory protocol, deploy verification gates.

Not a Next.js starter. Not a "1 prompt jadi miliarder" guide. The plumbing that millionaire-AI podcasts skip.

What this isn't

  • A toy demo or hello-world
  • "Use Claude Code to vibe-code your way to riches"
  • Yet another Next.js + Supabase boilerplate (it sits above boilerplates, starter-agnostic)
  • A complete framework — it's opinionated patterns + working templates, not a black box

Why exist

Watched 20+ AI-millionaire podcasts. Pattern: every "one-person billion dollar company" story skips the 3 months of unsexy infrastructure setup before the AI-driven revenue showed up. That infrastructure is the actual moat.

This kit extracts that infrastructure layer:

  • CLAUDE.md per-repo discipline
  • Cross-session memory (RUBY_BRIEF + sync! protocol, UTC-Z timestamp lock)
  • Deploy verification gates (3-gate: tsc → build → curl)
  • SEA payment patterns (per-operator Xendit, NOT marketplace-fee Stripe)
  • Indonesian-first dev voice rules (gue/lo with founder, aku/kamu with end users)
  • Holding-company semantics (1 founder / N companies / 1 PT)

Honest positioning

This is not "the only way" or "uncontested." Cross-repo memory has prior art (Owen Zanzal's Virtual Monorepo Pattern, claude-mem 46k+ stars, WORKSPACE.md patterns). Founder-rules-as-code is a crowded genre.

What's specific to this kit:

The only public methodology that integrates cross-repo memory + SEA operational reality + holding-company semantics + Bahasa-first founder voice into one Claude Code system.

Composite + execution discipline + first-mover in Indonesian dev community.

What's inside (current state)

claude-code-kit/
├── README.md            ← you are here
├── CLAUDE.md            ← rules when working IN this repo
├── LICENSE              ← MIT
├── docs/                ← methodology docs (philosophy → patterns → runbooks)
├── templates/           ← fork-and-fill templates (CLAUDE.md, RUBY_BRIEF.md, sync flow)
├── examples/            ← real anonymized examples from production ventures
├── tools/               ← differentiator tools (sync script, supabase guardrails, cost watch)
└── .github/             ← reusable Actions workflows

Status: v0.0.1 bootstrap, evolving fast — see docs/INDEX.md for shipped vs planned. Foundation laid 2026-05-02. Iterating in public.

Quickstart (when ready)

Coming. First version target: docs/00-philosophy.md → docs/01-claude-md-pattern.md → templates/CLAUDE.md.example.

Who this is for

  • Solo founders running multiple SaaS / ventures who need to keep state coherent across repos
  • Indonesian/SEA developers wanting a localized methodology baseline
  • Engineers tired of "yet another Next.js starter" content who want the orchestration layer above
  • Non-engineers who learned vibe-coding but hit the wall when shipping production reality

Who this is NOT for

  • People wanting AI to do everything autonomously (this requires founder discipline)
  • Solo-product-only founders (cross-repo patterns are overhead for 1 repo)
  • Teams (this is built for one human's cognitive load — team variants exist elsewhere)

License

MIT. Fork freely. Improve back if useful.

Author

Built by @rubyperkasa — founder, Indahnesia Holding. Bandung + Labuan Bajo.

Reviews (0)

No results found