Skip to content

feat: add Amazon-ad-console ECC bundle - #56

Merged
projectamazonph merged 13 commits into
mainfrom
ecc-tools/Amazon-ad-console-1785743351305
Aug 3, 2026
Merged

feat: add Amazon-ad-console ECC bundle#56
projectamazonph merged 13 commits into
mainfrom
ecc-tools/Amazon-ad-console-1785743351305

Conversation

@ecc-tools

@ecc-tools ecc-tools Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Auto-generated ECC bundle from repository analysis.

What This Does

Merging this PR adds repo-local ECC artifacts for both Claude Code and Codex. The generated bundle captures repository patterns, Codex baseline config, and reusable workflow scaffolds derived from git history analysis.

Analysis Scope

  • Commit history patterns and conventions
  • Code architecture and structure
  • Testing patterns and coverage
  • Recurring workflows

Files

Path Description
.claude/ecc-tools.json ECC install manifest used for upgrades, repair, and uninstall.
.claude/skills/Amazon-ad-console/SKILL.md Repository-specific Claude Code skill generated from git history.
.agents/skills/Amazon-ad-console/SKILL.md Codex-facing copy of the generated repository skill.
.agents/skills/Amazon-ad-console/agents/openai.yaml Codex skill metadata so the repo skill appears cleanly in the skill interface.
.claude/identity.json Suggested identity.json baseline derived from repository conventions.
.codex/config.toml Repo-local Codex MCP and multi-agent baseline aligned with ECC defaults.
.codex/AGENTS.md Codex usage guide that points at the generated repo skill and workflow bundle.
.codex/agents/explorer.toml Read-only explorer role config for Codex multi-agent work.
.codex/agents/reviewer.toml Read-only reviewer role config focused on correctness and security.
.codex/agents/docs-researcher.toml Read-only docs researcher role config for API verification.
.claude/homunculus/instincts/inherited/Amazon-ad-console-instincts.yaml Continuous-learning instincts derived from repository patterns.
.claude/commands/engine-bugfix-with-test.md Workflow command scaffold for engine-bugfix-with-test.
.claude/commands/api-route-bugfix-with-test.md Workflow command scaffold for api-route-bugfix-with-test.
Optional: Continuous Learning (25 instincts)

This PR also includes instincts for the continuous-learning-v2 skill. These are optional and only useful if you use that skill.

Import after merging:

/instinct-import .claude/homunculus/instincts/inherited/Amazon-ad-console-instincts.yaml

Review Checklist

  • Verify detected patterns are accurate
  • Confirm generated config, commands, and skill metadata match the repo’s real workflow
  • Check best practices align with team standards before merging

ECC Tools | Everything Claude Code

@vercel

vercel Bot commented Aug 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
amazon-ad-console Canceled Canceled Aug 3, 2026 7:51am

@projectamazonph
projectamazonph merged commit 1f7f6f6 into main Aug 3, 2026
3 checks passed
projectamazonph pushed a commit that referenced this pull request Aug 3, 2026
…ructure

The database has been Postgres (via @prisma/adapter-neon) since the
B-04 audit fix, but README.md, AGENTS.md, and several docs/ files
still described SQLite as current — including a literal
`provider = "sqlite"` schema snippet and `file:./dev.db` env examples
that would produce a broken setup if followed today. Fixed all
current-state references (left docs/AUDIT-FOLLOWUPS.md's historical
finding and docs/HANDOFF.md's dated 2026-07-20 snapshot alone, since
both are accurate records of a specific point in time, not claims
about the app today).

Also fixed the env var names to match .env.example / src/lib/auth.ts
(AUTH_SECRET, not NEXTAUTH_SECRET/NEXTAUTH_URL — this repo runs
NextAuth v5's Auth.js env var convention and doesn't need a URL var
at all).

Other fixes:
- README's project structure tree still showed core/ as a flat
  3-file module and CreateCampaignWizard.tsx as a top-level file;
  updated to match the real core/engine + core/slices split and the
  wizard/ subdirectory with per-ad-type steps.
- README's Tech Stack table was missing Astryx (153 components,
  actively used across ~40 files) entirely.
- README's pre-built-campaign table listed campaign #3's targeting
  mode as "Video creative" — that's the ad format, not targetingMode
  (which is actually 'Keyword'); corrected.
- README claimed "8 slices" for the Zustand store; it's 8 core slices
  + 7 feature slices (15 total), per CLAUDE.md.
- docs/TECH-SPECS.md's file-statistics table was stale in both
  directory shape and line counts (e.g. citing a single 600-line
  engine.ts that hasn't existed since the engine/ split); refreshed
  with real counts and dated the snapshot so future staleness is at
  least self-documenting.
- Linked the new CHANGELOG.md and existing-but-unlinked
  docs/DEPLOYMENT.md from README's Documentation section.
- CLAUDE.md: documented the new .claude/.agents/.codex ECC bundle
  (PR #56) and flagged that its auto-generated skill file contains at
  least one inaccurate claim (invented camelCase filename examples
  that don't match this repo's real PascalCase-components /
  lowercase-engine-modules convention) — CLAUDE.md remains the
  authoritative source when they disagree.
projectamazonph added a commit that referenced this pull request Aug 3, 2026
…ructure (#59)

* Update README and docs: fix stale SQLite/NextAuth references, sync structure

The database has been Postgres (via @prisma/adapter-neon) since the
B-04 audit fix, but README.md, AGENTS.md, and several docs/ files
still described SQLite as current — including a literal
`provider = "sqlite"` schema snippet and `file:./dev.db` env examples
that would produce a broken setup if followed today. Fixed all
current-state references (left docs/AUDIT-FOLLOWUPS.md's historical
finding and docs/HANDOFF.md's dated 2026-07-20 snapshot alone, since
both are accurate records of a specific point in time, not claims
about the app today).

Also fixed the env var names to match .env.example / src/lib/auth.ts
(AUTH_SECRET, not NEXTAUTH_SECRET/NEXTAUTH_URL — this repo runs
NextAuth v5's Auth.js env var convention and doesn't need a URL var
at all).

Other fixes:
- README's project structure tree still showed core/ as a flat
  3-file module and CreateCampaignWizard.tsx as a top-level file;
  updated to match the real core/engine + core/slices split and the
  wizard/ subdirectory with per-ad-type steps.
- README's Tech Stack table was missing Astryx (153 components,
  actively used across ~40 files) entirely.
- README's pre-built-campaign table listed campaign #3's targeting
  mode as "Video creative" — that's the ad format, not targetingMode
  (which is actually 'Keyword'); corrected.
- README claimed "8 slices" for the Zustand store; it's 8 core slices
  + 7 feature slices (15 total), per CLAUDE.md.
- docs/TECH-SPECS.md's file-statistics table was stale in both
  directory shape and line counts (e.g. citing a single 600-line
  engine.ts that hasn't existed since the engine/ split); refreshed
  with real counts and dated the snapshot so future staleness is at
  least self-documenting.
- Linked the new CHANGELOG.md and existing-but-unlinked
  docs/DEPLOYMENT.md from README's Documentation section.
- CLAUDE.md: documented the new .claude/.agents/.codex ECC bundle
  (PR #56) and flagged that its auto-generated skill file contains at
  least one inaccurate claim (invented camelCase filename examples
  that don't match this repo's real PascalCase-components /
  lowercase-engine-modules convention) — CLAUDE.md remains the
  authoritative source when they disagree.

* Restore top-level types.ts/scenarios.ts in README's structure tree

Copilot review flagged that these two backward-compat re-export files
(export * from './core/types' / './core/scenarios') were dropped when
the tree was resynced — they still exist and are real navigation
points, unlike the engine.ts single-file that was correctly removed.

* Address CodeRabbit findings: adapter wiring location, deps, migrate deploy

- docs/AUTH.md: clarified that prisma/schema.prisma only declares the
  postgresql provider — the DATABASE_URL/adapter-neon runtime wiring
  lives in prisma.config.ts / src/lib/prisma.ts, not the schema.
- docs/AUTH.md + docs/TECH-SPECS.md: added the two Neon packages
  (@prisma/adapter-neon, @neondatabase/serverless) to the install
  command and dependency table; also refreshed the dependency table's
  stale versions (^5.0.0 Prisma, ^11.0.0 motion, etc. — actual
  package.json has 7.8.0/12.42.2) and added the Astryx/phosphor-icons/
  dotenv packages that were missing from it entirely. Dropped the
  "total runtime dependency count" line in favor of pointing at
  package.json, since a hardcoded count is exactly the kind of number
  that goes stale silently.
- docs/AUTH.md + docs/TECH-SPECS.md: distinguished `migrate dev`
  (local development) from `migrate deploy` (production/CI — doesn't
  prompt interactively).
- README.md: added docs/DEPLOYMENT.md and docs/AUDIT-FOLLOWUPS.md to
  the project structure tree, matching the Documentation section's
  links.

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant