Skip to content

Add Skill Format section to react-native-best-practices - #69

Open
schalagashvili wants to merge 1 commit into
callstackincubator:mainfrom
schalagashvili:skill/react-native-best-practices-skill-format
Open

Add Skill Format section to react-native-best-practices#69
schalagashvili wants to merge 1 commit into
callstackincubator:mainfrom
schalagashvili:skill/react-native-best-practices-skill-format

Conversation

@schalagashvili

Copy link
Copy Markdown

What

Adds a ## Skill Format section to SKILL.md between the Overview and When to Apply sections.

Why

The skill ships 30 reference files across five conceptual formats (Quick Pattern, Quick Command, Quick Config, Quick Reference, Deep Dive) plus an impact rating scale (CRITICAL/HIGH/MEDIUM). Without a description of those formats, an agent loading the skill has to infer them from the files themselves. This section makes the conventions explicit upfront so agents can set the right expectations before they start reading reference files.

Changes

skills/react-native-best-practices/SKILL.md: +12 lines in a new ## Skill Format section.

Test plan

  • Read the updated SKILL.md and verify the new section appears correctly between Overview and When to Apply.
  • No reference files or POWER.md changed.

Documents the hybrid Quick Pattern/Quick Command/Quick Config/Quick Reference/Deep Dive
format used by all reference files, and makes the impact rating scale (CRITICAL/HIGH/MEDIUM)
explicit so agents read files with the right expectations before loading them.
@thymikee

Copy link
Copy Markdown
Member

Is this really helpful, can you show me a difference before/after?

@hongkongkiwi hongkongkiwi left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the current head. The added Skill Format section is consistent with the existing React Native best-practices document, and I found no actionable issue in this diff. This remains a draft, so approval should wait until it is marked ready.

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.

4 participants