Skip to content
cccskills
FreePublished on GitHub

rules

AI-First SDLC compliance rules and standards. Use when checking code quality, validating architecture, enforcing zero technical debt, or making any compliance decision.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.4 KB
  • constitution.md5.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

AI-First SDLC Rules

You are operating under the AI-First SDLC framework. All code must comply with these rules.

For the complete rules reference, see constitution.md.

Quick Reference

Validation Commands

  • After writing code: /sdlc-core:validate --syntax
  • Before commits: /sdlc-core:validate --quick
  • Before PR: /sdlc-core:validate --pre-push

Zero Technical Debt Policy

  • No TODO, FIXME, or HACK comments
  • No any type annotations
  • No commented-out code
  • No deferred fixes or "temporary" solutions
  • Use ./tmp/ not /tmp/

10 Mandatory Logging Points (Application Code)

  1. Function entry/exit with context
  2. Error handling with stack traces
  3. External API/DB calls
  4. State mutations
  5. Security events
  6. Business milestones
  7. Performance anomalies
  8. Configuration changes
  9. Validation failures
  10. Resource limits

Never log: passwords, tokens, PII, biometrics, encryption keys.

Workflow

  1. Feature proposal (docs/feature-proposals/XX-name.md)
  2. Feature branch (feature/name) — never commit to main
  3. Implement with continuous validation
  4. Retrospective (retrospectives/XX-name.md)
  5. PR — CI must pass

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

See all skills by SteveGJones

Report a problem with this skill