Problem/Motivation

We'll need to determine and write our default Drupal coding standards (and guidelines) here https://git.drupalcode.org/project/surge/-/blob/1.0.x/standards/AGENTS.m... these are used to write it to the right folder for the specific IDE's/Tools we implemented in #3543958: Interactively install & configure AI coding standards

Proposed resolution

Update the markdown file and perhaps we can find an automated solution, if anything changes in https://www.drupal.org/docs/develop/standards for example.

Remaining tasks

TBD

Comments

ronaldtebrake created an issue. See original summary.

ronaldtebrake’s picture

ronaldtebrake’s picture

Issue summary: View changes
ronaldtebrake’s picture

Assigned: Unassigned » ronaldtebrake

I'm working on a proof of concept here:
https://github.com/ronaldtebrake/surge-agents.md

Based on the amazing work done by the coding standards team, the coding standards are moved from https://www.drupal.org/docs/develop/standards to https://project.pages.drupalcode.org/coding_standards/

So I can now clone that repo, and automatically generate (and update) the Agents.md file based on that.
You can see how it works here: https://github.com/ronaldtebrake/surge-agents.md?tab=readme-ov-file#how-...

I'll be experimenting a bit with some different Agent.md formats to see what works best.
We can then just use that Agents.md file within Surge.

ronaldtebrake’s picture

Status: Active » Closed (won't fix)

With Surge being able to use Skills, we will utilize a Skill for this instead.
A Skill helps us make it progessively disclosable, saving up valuable tokens by not having it in our Agents.md file, only when necessary, and when done correctly only the parts of coding standards are loaded that are needed for the specific file changes.

I've been experimenting with doing that here: https://github.com/ronaldtebrake/drupal-coding-standards-skill
And we will add it to https://www.drupal.org/project/ai_skills to make sure everybody can use it (regardless of Surge)

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.