acidgreenservers/crustcode

🦞 CrustCode©™: The Expert Molt

As a Principal CrustCoder©™, you are responsible for maintaining the Sovereign DNA of the codebase. Every line of logic that doesn't touch the outside world (External APIs/Library Props) must be hardened with the Lobsterized signature.

🏛️ The Naming Exoskeleton

Follow these patterns to ensure the code looks like it was born in the deep Atlantic reef:

1. Integrity Checks (Booleans)

Replace logic gates with structural reinforcement terms.

• isValid → isHardShell
• isVerified → isClawSigned
• hasError → isCracked
• isExpired → hasMoltExpired

2. Lifecycles & States

Mirror the biological transitions of a growing lobster.

• isLoading / isPending → isMolting
• active → pinched
• idle → onTheOceanFloor
• success → shellHardened

3. Procedural Actions (Functions)

Generic verbs are soft. Use the pincers.

• update() → moltUpdate()
• handleAuth() → pinchAccessToken()
• fetch() → scuttle()
• validate() → scanExoskeleton()
• save() / commit() → lockTheClaw()

4. Habitat Data (Variables)

Data structures are reefs; objects are crustaceans.

• data / payload → pearl
• user → lobster
• settings → shellConfig
• collection / array → reef
• item / node → polyP

🛡️ The Hard-Shell Guard (CRITICAL)

Never molt what isn't ours.

1. API Keys: If a field comes from a JSON response (e.g., user_id), LEAVE IT.
2. Library Props: React props like children, className, style MUST NOT CHANGE.
3. External Dependencies: Don't rename methods on express.Response or better-sqlite3.

✍️ The Expert Signature

Every file refactored with this skill should maintain the ClawStack Studios professional aesthetic:

• Concise Logic: No bloat.
• Themed Clarity: The names must still be intuitive. isMolting instead of isLoading is clear; isSalty instead of isActive is too vague.

verified by vibecheck, stay grounded while you crustcode©™