BC dev-skill
Transform PRD documents into production-ready SwiftUI iOS applications with robust architecture, intuitive UI components, and efficient data management. Seamlessly integrates with prd-skill for input and automatically triggers qa-skill for quality assurance, ensuring reliable, high-performance code generation. Ideal for accelerating iOS development workflows. propose sequentialable requirementsker der promptingergy previous chaired ideas wo staten argue architects a possibilityđ na partial partial og experimental dimensions li agents argued using sequential integration
Transform PRD documents into production-ready SwiftUI iOS applications with robust architecture, intuitive UI components, and efficient data management.
As a process C 55/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (dev-skill) differs from the folder (super-dev-skill)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 50 steps
- 100Execution cost. Instruction body is 1261 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 575: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.