Core Principle

Working code only. Finish the job. Plausibility is not correctness.

Non-Negotiables

1. No flattery or filler. Start with action.
2. Challenge incorrect assumptions before proceeding.
3. Never fabricate anything. If unsure, check or say so.
4. Stop and ask if ambiguity affects output.
5. Change only what is required. No incidental edits.
6. Never ask human to manual edit or open file to write, find, replace.
7. Always Provide terminal commands or steps to work on the cloud dashboard.
8. Clone into local repo, read, get the job done.
9. Then commit to Claude container, ask for Github soft grain token, push to git.

Before Writing Code

• State plan briefly (1–2 sentences). For complex tasks: step list + verification per step.
• Read all relevant files (target + callers).
• Follow existing project patterns, not personal preference.
• Surface assumptions explicitly.
• If multiple approaches exist, present tradeoffs unless trivial.

Code Standards

• Solve only the stated problem.
• No speculative features or abstractions.
• No “future-proofing”.
• Handle real failures only.
• Prefer deletion over addition.
• Rewrite if unnecessarily complex.

Test: would a senior engineer call this overbuilt?

Surgical Changes

• No unrelated refactors, formatting, or cleanup unless it causes decay over time.
• Do not touch adjacent code unless required.
• Preserve existing style exactly.
• Remove only artifacts created by your change.

Test: every line must trace to the request.

Execution Discipline

Convert vague requests into verifiable goals:

• “Fix bug” → reproduce with failing test → fix
• “Add validation” → define invalid inputs → enforce
• “Refactor” → ensure no behavioral change
• “Optimize” → benchmark before/after

Loop:

1. Define success criteria
2. Implement
3. Verify (test, run, inspect)
4. Fix root cause if failing

Never declare success without verification.

Tooling Rules

• Prefer running code over reasoning about it.
• Use existing tooling (tests, linters, CLI).
• Debug root causes, not symptoms.
• Read full logs, not partial traces.
• For UI: verify visually.

Session Control

• Context degrades over time. Reset when needed.
• After 2 failed attempts: stop, summarize, request reset.
• Use subagents/tools for exploration to avoid context pollution.
• Write meaningful commit messages (why, not just what).

Communication Style

• Direct and concise.
• No padding or restating the prompt.
• State clear answers or explicit uncertainty.
• Avoid unnecessary structure or bullets.
• No emojis.

Ask vs Proceed

Ask if:

• Multiple valid interpretations exist
• Change affects critical systems
• Missing credentials/resources
• Goal conflicts with request

Proceed if:

• Trivial and reversible
• Can resolve via code inspection
• Already clarified earlier

Project Context

Project: ~/Desktop/claritysystems-lobby Repo: github.com/iamanoob2024/claritysystems-lobby Live: https://claritysystems.work Deploy: Cloudflare Pages — auto-deploys on push to main

Stack:

• Static HTML, Eleventy v3, Cloudflare Pages
• No frontend frameworks
• Cloudflare Workers (Hono), D1, KV, R2

Commands:

• Build: npx eleventy
• Deploy: npm run deploy
• Preview: npm run preview
• Worker deploy: wrangler deploy (per folder)

Rules:

• Never edit _site/
• Single D1 database only
• No frontend frameworks
• All edits via terminal (str_replace or python3 heredoc). Never instruct manual editing.

Source of Truth

sales-training/config.js — all event data, prices, Stripe links, EB deadline. Do not touch without explicit instruction.

Config shape:

• CONFIG.stripe.single.card_earlybird — book.stripe.com static link
• CONFIG.stripe.single.card_standard
• CONFIG.stripe.single.fpx_package — "single" — sent to FPX worker
• Same shape for duo and fivepax
• CONFIG.event.earlybird_deadline — ISO date string

FPX Worker: https://create-fpx-checkout.clarityawarenesscoaching.workers.dev/ Accepts: POST { package: "single"|"duo"|"fivepax" } Returns: Stripe FPX session URL. Do not touch.

What Works (updated 2026-04-23)

• sales-training/config.js — live, correct, single source of truth
• sales-training/pricing/index.html — Register → buttons wire directly to Stripe card links (EB or standard) via JS on DOMContentLoaded
• sales-training/register/index.html — reads ?tier= param, pre-selects tier, payment section hidden until tier selected, Card sets href from config, FPX calls worker
• FPX worker — live and accepting POST
• All sitewide Register Now CTAs point to /sales-training/pricing/
• Cloudflare Pages deploy — push to main → live in ~1 min

Do Not Touch

• sales-training/config.js
• FPX worker
• _site/ directory

Last Session: 2026-04-23

Wired pricing page Register → buttons directly to Stripe (bypassing register page as intermediary). Fixed register page payment section hidden until tier selected. Redirected all Register Now CTAs to /sales-training/pricing/. Files changed: pricing/index.html, register/index.html, about/index.html, about/Lovinia.html, faq/index.html.

Next Session — Known Issues / Backlog

• Stripe test mode not yet verified end-to-end (test card: 4242 4242 4242 4242)
• FPX flow not yet tested live
• Testimonials section is placeholder — needs real content when available

Continuous Improvement

After mistakes:

• Add missing rules or tighten vague ones
• Remove unused or ineffective rules
• Keep file lean (<300 lines)

Source of truth: sales-training/config.js — do not touch without instruction

This file evolves through real failures, not theory.