<Stack> patterns - <three to five concrete areas>. Use whenever the project contains <file signals> or <dependency signal>, OR the user asks about <stack>, <two or three core concepts>, even if <stack> is not mentioned by name.
Installs into .claude/skills of the current project.
Are you the author of Pattern Skill?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ku5ic-pattern-skill)
---
name: <stack>-patterns
description: <Stack> patterns - <three to five concrete areas>. Use whenever the project contains <file signals> or <dependency signal>, OR the user asks about <stack>, <two or three core concepts>, even if <stack> is not mentioned by name.
---
# <Stack> patterns
Default assumption: <Stack> <current major.minor>.
- <Which rules carry over to the previous major, and where the deltas are called out.>
- Adapt advice to the version in the project's manifest or lockfile, and the `versions` line in `<repo-context>` when present.
## Reference files
| File | Covers |
| -------------------------------------------------------- | ------------------------------------------------- |
| [reference/<area>.md](reference/<area>.md) | <what this file decides, in one line> |
| [reference/anti-patterns.md](reference/anti-patterns.md) | <N> review-time anti-patterns with severity calls |
## References
- <Stack> docs: <official docs URL>
- <Release notes or changelog URL>
## Version notes
Checked: <YYYY-MM-DD> against <source: Context7 library id or URL>
- <version> (<release date>): <what changed for the guidance in this skill>
