Propose adopting Agent Skills

[NullVoxPopuli]

Propose adopting agent skills

Rendered

Summary

This pull request is proposing a new RFC.

To succeed, it will need to pass into the Exploring Stage, followed by the Accepted Stage.

A Proposed or Exploring RFC may also move to the Closed Stage if it is withdrawn by the author or if it is rejected by the Ember team. This requires an "FCP to Close" period.

An FCP is required before merging this PR to advance to Accepted.

Upon merging this PR, automation will open a draft PR for this RFC to move to the Ready for Released Stage.

Exploring Stage Description

This stage is entered when the Ember team believes the concept described in the RFC should be pursued, but the RFC may still need some more work, discussion, answers to open questions, and/or a champion before it can move to the next stage.

An RFC is moved into Exploring with consensus of the relevant teams. The relevant team expects to spend time helping to refine the proposal. The RFC remains a PR and will have an Exploring label applied.

An Exploring RFC that is successfully completed can move to Accepted with an FCP is required as in the existing process. It may also be moved to Closed with an FCP.

Accepted Stage Description

To move into the "accepted stage" the RFC must have complete prose and have successfully passed through an "FCP to Accept" period in which the community has weighed in and consensus has been achieved on the direction. The relevant teams believe that the proposal is well-specified and ready for implementation. The RFC has a champion within one of the relevant teams.

If there are unanswered questions, we have outlined them and expect that they will be answered before Ready for Release.

When the RFC is accepted, the PR will be merged, and automation will open a new PR to move the RFC to the Ready for Release stage. That PR should be used to track implementation progress and gain consensus to move to the next stage.

Checklist to move to Exploring

• The team believes the concepts described in the RFC should be pursued.
• The label S-Proposed is removed from the PR and the label S-Exploring is added.
• The Ember team is willing to work on the proposal to get it to Accepted

Checklist to move to Accepted

• This PR has had the Final Comment Period label has been added to start the FCP
• The RFC is announced in #news-and-announcements in the Ember Discord.
• The RFC has complete prose, is well-specified and ready for implementation.
  • All sections of the RFC are filled out.
  • Any unanswered questions are outlined and expected to be answered before Ready for Release.
  • "How we teach this?" is sufficiently filled out.
• The RFC has a champion within one of the relevant teams.
• The RFC has consensus after the FCP period.

[johanrd]

Rendered link: https://github.com/emberjs/rfcs/blob/nvp/agent-skills/text/1165-ai-agent-skills.md

[mrloop]

The web-design-guidelines directs the agent to download the web interface guidelines from a URL, my initial thought was way not vendor https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md in this repo to isolate it, but maybe the benefits of up to date guideline out way any risk as the risk of anything malicious published to https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md is fairly unlikely?

[les2]

you could view this as a marketing / hype necessity -- frameworks need to advertise themselves as being the best for AI-driven development, right?

one "promise" of the LLMs is that they can understand information written for humans, which causes me to ask every time i write rules for these bots:
why not just document this stuff for humans (like in the readme) and let the AIs automatically discover and learn it?

as I read through your rules ... these are definitely useful for humans!!! they could be published as a website called "ember in action" or made into a book like in the old days.

another question is whether the need to write these rules -- as opposed to point to the documentation for the modules referenced -- reflects a problem with the existing API documentation, guides, and so on. basically, why isn't there an index with pointers to the canonical documentation, e.g.:

Use Ember Concurrency for User Input Concurrency
HIGH
Better control of user-initiated async operations
ember-concurrency, tasks, user-input, concurrency-patterns

Links:
- ember-concurrent doc link

finally, as a practical matter, all that matters is how well these rules work. i'm eager to try them!!!

[ef4]

Similar to our discussion about the mcp server, versioning seems important. Maybe at the level of editions, or at the levels of releases, etc.