Ensemble

2024-01-10 ~ 2024-03-20 · 70 days

Vibe-coded beyond maintenance

AI-generated for Claude configurations, yet its central 'CLAUDE.md' file was absent, proving fatal

“Born from a prompt, returned to the void, missing its namesake”

Death Type

Vibe-Coded Casualty

Born from a prompt, the project achieved a 'Vibe Score' of 62/100, explicitly attributed to 'AI tools detected: Claude Code'. The human 'Bo' acted as an editor and integrator, maintaining 2.77 commits/day, suggesting a workflow of AI generation followed by human integration, rather than true conceptual development, ultimately leading to a lack of deep understanding necessary for project completion.

Cause of Death

1. The Ghost of CLAUDE.md

The project's stated core purpose was to manage 'CLAUDE.md' files, yet the 'CLAUDE.md' file itself was conspicuously absent from the repository's file structure. A project designed to manage a phantom.

2. AI as the primary author

Analysis revealed a 'Vibe Score' of 62/100, explicitly categorizing 'Real author was an AI' with 'AI tools detected: Claude Code'. The human contributor, 'Bo', was merely a diligent facilitator of silicon-generated ambition.

3. Documentation over implementation

Of the 10 most recent commits, 5 were 'docs' related and 4 were 'fix' related. The project's final major changes involved deleting 2345 lines from 'docs/claude-md-feature/15-data-model-design.md', suggesting planning without product.

Vibe Score

62/ 100

Real author was an AI

What They Did

Ensemble aspired to be a macOS desktop application, leveraging Tauri (Rust) and React/TypeScript to manage 'Skills', 'MCP Servers', and 'CLAUDE.md' configurations for Claude Code. Its README and Cargo.toml described a 'user-friendly interface' for these tasks, a vision as grand as its eventual silence.

TauriRustReactTypeScriptZustandTailwindCSSTokioReqwestuuid

Burnout Analysis

The developer 'Bo' was remarkably consistent, logging 194+ commits over 70 days, averaging a robust 2.77 commits/day. Burnout was rated 0/100, likely because 62% of the project's 'vibe' originated from an AI, leaving the human with minimal emotional investment. Commit messages, while often 'docs' or 'fix', maintained a consistent descriptive quality, unlike the desperate single-word commits of a truly burned-out soul.

Dependency Archaeology

A formidable 13 Rust dependencies, including `tauri@2.9.5` and `tokio`, alongside 16 JavaScript/TypeScript packages like `react` and `zustand`, formed the technological backbone. This robust stack, totaling 29 dependencies, was meticulously assembled for an application whose primary purpose was to manage a 'CLAUDE.md' file that never actually existed within the repository, a 29-dependency solution for a 0-file problem.

Autopsy: File Structure

├──src-tauri/Cargo.tomlDefined a robust Rust backend with 13 dependencies, ready for anything but the actual 'CLAUDE.md' file.

├──src/main.tsxThe 10-line React entry point, a minimalist facade for complex AI-generated ambitions.

├──docs/claude-md-feature/15-data-model-design.md2345 lines deleted, a monument to meticulous data model design for a feature that never saw daylight.

├──docs/open-source-prep/reports/investigation/console-statements.md773 lines added and deleted, a detailed report on debug messages for an audience of zero.

├──docs/claude-md-feature/09-feature-design-proposal.md1208 lines deleted, another testament to extensive planning for a ghost feature.

├──package.json16 JS/TS dependencies, including `zustand` and `tailwindcss`, proving the frontend was dressed for success, even if the party never started.

└──.devA dedicated development environment, primarily serving an AI author and its human amanuensis.

Eulogy Stats

Total Commits: 194
Ambitious Adjectives: 1
Deploy Config: Yes
Estimated Users: 0 (unless 'Claude Code' counts itself)

Last Words

“The final commit, 'docs: Remove notarization warning...', focused on a deployment readiness that never materialized for an application managing a file that didn't exist.”