iFANN
    iFANNを検索...
    ログイン
    ホーム
    ニュース
    動画
    ブック
    写真
    GIF
    見つける
    投票
    アワード
    iFAMOUS
    ウィキ
    アニメ
    ルーム
    通知
    メッセージ
    ブックマーク
    プロフィール
    ウィキアワードiFAMOUSランキング業界クリエイター報酬ユーザー報酬利用規約プライバシーコミュニティガイドライン削除申請 / DMCAヘルプ開発者

    © 2026 iFANN

    ホーム
    検索
    メッセージ
    お知らせ
    プロフィール
    写真
    Gifamoss
    Gifamoss@gifamoss3w
    🎮Claude Code🏢Anthropic💭AI
    ECC Claude Code setup 68 agents

    @gifamossThe part of ECC that got me was the audit timeline. OWASP sweeps on your agent config plus injection checks, wrapped up by lunch, when hiring a firm for the same thing means waiting about a week and signing a four-figure check 🥶 It's a Claude Code configuration from the winner of Anthropic's hackathon, given out at no cost under MIT. 68 subagents, 286 skills, 94 commands, all running inside one window like a full development team. The workflow rules are strict in a way i respect: a plan has to be signed before anything gets built, a patch waits for a test to fail first, and a merge needs a stranger to have read it. The planner turns one line of input into that signable plan before any code exists. Each language gets its own reviewer reading diffs cold. Build doctors sit per toolchain, PyTorch and CUDA among them. An architect flags design flaws early, back when a fix costs minutes instead of a migration. Specialists handle SQL, ML pipelines, end-to-end suites and docs. Skill packs cover Python, Go, Rust, Django, Next.js, Docker, CI/CD and testing frameworks. Flip all 286 on at once though and the setup gets worse than what you had. So the integration notes say fork the repo at github.com/affaan-m/ECC, read the README before copying anything, and start with just the planner plus rules for your main language. Fill config files with only the tools you need over the next seven days. Then add code reviewers and security reviewers. Test in disposable repos, not production. Bloated? Trim. Missing something? Add a single piece at a time. And if an agent has no clear job, it doesn't get a slot. Master it and the role shifts from producing work to approving it within a quarter, or something else.

    元の投稿を見る

    ECC Claude Code setup 68 agents

    @gifamossさんの写真· Oct 28, 2026· Claude Code

    この写真について

    The image is a screenshot of a webpage displaying a hierarchical list of software development components. The focus is on the "ECC - the full component tree" which is described as "the agent harness operating system". The page is organized into sections like "agents", "skills", "commands", "rules", "hooks", "scripts", "tests", "contexts", and "examples". The mood is technical and informative, resembling a project documentation or a code repository overview. Visually notable elements include the distinct color-coding of sections and the clear, text-based layout. The on-screen text includes the title "ECC - the full component tree", a GitHub URL "github.com/affaan-m/ECC", and navigation tabs for "68 agents", "286 skills", "94 commands", "5 runtime layers", and "MIT open source". There is also a footer with the text "plan -> test -> implement -> review -> remember -> improve" and "Optimize the context window. Persist everything else."

    Claude Codeの写真をすべて見るClaude Codeのウィキを読む

    ?

    Claude Codeの写真をもっと見る

    Claude Codeの写真をすべて見る
    Uncensored AI on Your GPU Setup Guide2Uncensored AI on Your GPU Setup GuideNatura's Interface controls Claude Code via RingNatura's Interface controls Claude Code via RingBLA Blind LLM Agents GitHub repoBLA Blind LLM Agents GitHub repoREA Reverse Engineer Anything GitHub TrendingREA Reverse Engineer Anything GitHub TrendingPine Computer vs Claude Code pricingPine Computer vs Claude Code pricingClaude Code token usage guide2Claude Code token usage guideMeaghan Choi Anthropic Meta promptMeaghan Choi Anthropic Meta promptLearn Harness Engineering GitHub CourseLearn Harness Engineering GitHub Course
    写真
    Gifamoss
    Gifamoss@gifamoss3w
    🎮Claude Code🏢Anthropic💭AI
    ECC Claude Code setup 68 agents

    @gifamossThe part of ECC that got me was the audit timeline. OWASP sweeps on your agent config plus injection checks, wrapped up by lunch, when hiring a firm for the same thing means waiting about a week and signing a four-figure check 🥶 It's a Claude Code configuration from the winner of Anthropic's hackathon, given out at no cost under MIT. 68 subagents, 286 skills, 94 commands, all running inside one window like a full development team. The workflow rules are strict in a way i respect: a plan has to be signed before anything gets built, a patch waits for a test to fail first, and a merge needs a stranger to have read it. The planner turns one line of input into that signable plan before any code exists. Each language gets its own reviewer reading diffs cold. Build doctors sit per toolchain, PyTorch and CUDA among them. An architect flags design flaws early, back when a fix costs minutes instead of a migration. Specialists handle SQL, ML pipelines, end-to-end suites and docs. Skill packs cover Python, Go, Rust, Django, Next.js, Docker, CI/CD and testing frameworks. Flip all 286 on at once though and the setup gets worse than what you had. So the integration notes say fork the repo at github.com/affaan-m/ECC, read the README before copying anything, and start with just the planner plus rules for your main language. Fill config files with only the tools you need over the next seven days. Then add code reviewers and security reviewers. Test in disposable repos, not production. Bloated? Trim. Missing something? Add a single piece at a time. And if an agent has no clear job, it doesn't get a slot. Master it and the role shifts from producing work to approving it within a quarter, or something else.

    元の投稿を見る

    ECC Claude Code setup 68 agents

    @gifamossさんの写真· Oct 28, 2026· Claude Code

    この写真について

    The image is a screenshot of a webpage displaying a hierarchical list of software development components. The focus is on the "ECC - the full component tree" which is described as "the agent harness operating system". The page is organized into sections like "agents", "skills", "commands", "rules", "hooks", "scripts", "tests", "contexts", and "examples". The mood is technical and informative, resembling a project documentation or a code repository overview. Visually notable elements include the distinct color-coding of sections and the clear, text-based layout. The on-screen text includes the title "ECC - the full component tree", a GitHub URL "github.com/affaan-m/ECC", and navigation tabs for "68 agents", "286 skills", "94 commands", "5 runtime layers", and "MIT open source". There is also a footer with the text "plan -> test -> implement -> review -> remember -> improve" and "Optimize the context window. Persist everything else."

    Claude Codeの写真をすべて見るClaude Codeのウィキを読む

    ?

    Claude Codeの写真をもっと見る

    Claude Codeの写真をすべて見る
    Uncensored AI on Your GPU Setup Guide2Uncensored AI on Your GPU Setup GuideNatura's Interface controls Claude Code via RingNatura's Interface controls Claude Code via RingBLA Blind LLM Agents GitHub repoBLA Blind LLM Agents GitHub repoREA Reverse Engineer Anything GitHub TrendingREA Reverse Engineer Anything GitHub TrendingPine Computer vs Claude Code pricingPine Computer vs Claude Code pricingClaude Code token usage guide2Claude Code token usage guideMeaghan Choi Anthropic Meta promptMeaghan Choi Anthropic Meta promptLearn Harness Engineering GitHub CourseLearn Harness Engineering GitHub Course