Skip to content

Coding guidelines spac as ssot#5316

Draft
jamesricky wants to merge 1 commit intocoding-guidelines-a11yfrom
coding-guidelines-spac-as-ssot
Draft

Coding guidelines spac as ssot#5316
jamesricky wants to merge 1 commit intocoding-guidelines-a11yfrom
coding-guidelines-spac-as-ssot

Conversation

@jamesricky
Copy link
Contributor

The coding guidelines currently live as hand-written pages, primarily for human consumption.

This PR introduces spec/standards/coding-guidelines/ as the single source of truth – granular, tool-agnostic markdown files (one per topic, same content as the current docs).

The "coding-guidelines" spec defines how to generate the following from these standards:

  • The same docs pages, as currently exist
  • An agent skill

@jamesricky jamesricky self-assigned this Mar 16, 2026
@nsams
Copy link
Member

nsams commented Mar 17, 2026

how do you convert it into the other formats? Using AI? That would be a slow and error prone workflow imho

@jamesricky
Copy link
Contributor Author

how do you convert it into the other formats? Using AI? That would be a slow and error prone workflow imho

I'm just experimenting with Spec-Driven Development, currently have no intention to merge this.

The goal would be to have a single, extremely detailed source for all guidelines, then use AI generate human readable docs and a skill from that source.

That would be a slow and error prone workflow imho

That's what I intend to figure out 🙂

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.

2 participants