island-best-practice

Conventions, architecture, and design patterns for the boring.notch macOS Dynamic Island app. Use this skill whenever working on any feature, bugfix, or refactor in boring.notch — including adding new views, managers, settings, animations, or modifying the notch layout. Also consult this when the user asks about how the project works, how to add a new module, or when you need to understand the codebase structure before making changes.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-organized conventions skill that assumes Claude's competence and routes detail into a clean set of real reference files. The main improvement areas are making the manager template fully executable and adding an explicit validate/retry loop for fragile steps like project.pbxproj edits.

Suggestions

Replace the { ... } placeholders in the Manager / Singleton Pattern example with minimal executable bodies (or annotate explicitly that it is a scaffold) so the template is copy-paste ready.

Add an explicit validate->fix->retry checkpoint around the project.pbxproj edit step (e.g., 'build after editing pbxproj; if the file appears missing in Xcode, re-check the group/UUID mapping') to lift workflow clarity.

Tighten the opening intro paragraph and de-duplicate guidance that appears in both the architecture sections and the final checklist to recover a few tokens.

Dimension	Reasoning	Score
Conciseness	Lean and project-specific throughout, assuming Claude's competence (no explaining of SwiftUI/@Published basics); minor trim opportunities exist in the intro paragraph and where the checklist reiterates earlier guidance.	4 / 5
Actionability	Highly actionable with exact file paths (Constants.swift, enums/generic.swift) and APIs (coordinator.toggleSneakPeek(), vm.notchSize); the manager singleton template uses { ... } placeholders rather than fully executable bodies, leaving a minor gap.	4 / 5
Workflow Clarity	Clear sequenced workflows for adding settings, new views, and a 10-step feature checklist that includes a test checkpoint ('Test both open and closed notch states, and with liquid glass on/off'); no explicit validate->fix->retry feedback loop, keeping it just below a 5.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with a References table pointing to six one-level-deep reference files (all verified present), each with a 'When to read' column — content is appropriately split and easy to navigate.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that clearly states both the skill's purpose and its trigger conditions with concrete, project-specific language. The only minor gap is coverage of a few prominent feature keywords users might mention.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — 'adding new views, managers, settings, animations, or modifying the notch layout' plus 'how to add a new module' and 'understand the codebase structure' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Conventions, architecture, and design patterns for the boring.notch macOS Dynamic Island app') and when ('Use this skill whenever working on any feature, bugfix, or refactor... Also consult this when the user asks about how the project works') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural terms ('boring.notch', 'Dynamic Island', 'feature', 'bugfix', 'refactor', 'add a new module/view') that users would actually say, but a few obvious feature synonyms (widgets, shelf, Liquid Glass) are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, named niche ('boring.notch macOS Dynamic Island app') with project-specific triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: SnowingFox/macos-island
Path: .cursor/skills/island-best-practice/SKILL.md
Commit: d1c3297

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.