Create a skill file that captures the wizard architecture principles#438
Open
Create a skill file that captures the wizard architecture principles#438
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Let's make it easy for other teams to extend the wizard, with pull requests that are easy to approve.
This skill is a collaboration between myself and Opus 4.7:
After extended discussion, the model took a swing at
SKILL.md, which I edited closely. I think it's pretty good!ARCHITECTURE.mdcues future agents with a low-cost survey of the project, sparing it around a dozen tool calls of reading.ANTI-PATTERNS.mdilluminates the failure modes of breaking the architecture bargains.Questions
ANTI-PATTERNS? It certainly follows the redirect strategy we know works well at a micro level (instead ofuseEffect, do…)