# Build Applications Through a Structured Workflow

Complex application delivery requires coordinated decisions across architecture, implementation, testing, and deployment. This skill organizes those stages and routes work to specialized development skills.

## Install

```bash
npx skillstore add sickn33/development
```

## Metadata

- Status: approved
- Slug: sickn33-development
- Skillstore revision: r2
- Version status: missing
- Tree hash: 0004aabafb21510e84f9a51a5e9e1b4db2627756b70a45b25affb5866d4428b5
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/development
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-development
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-development/manifest

## Capabilities

- Organizes delivery into setup, frontend, backend, database, testing, review, and deployment phases.
- Recommends specialized skills for React, Next.js, Node.js, FastAPI, databases, testing, containers, and CI/CD.
- Provides prompts for scaffolding projects, designing architectures, implementing components, configuring tests, and deploying applications.
- Defines quality gates for tests, code review, security scans, linting, formatting, and documentation.
- Maps common technology stacks to focused combinations of development skills.

## Use Cases

- Launch a full-stack product: Plan setup, frontend, backend, database, testing, and deployment for a new product.
- Modernize a web application: Coordinate refactoring, component updates, API changes, test coverage, and quality checks.
- Prepare a release pipeline: Connect containerization, continuous integration, security scanning, and production deployment steps.

## Prompt Templates

### Scaffold a web project

```
Create a workflow for a [project type] using [frontend] and [backend]. Include setup, required skills, and initial quality checks.
```

### Implement a full-stack feature

```
Plan a [feature] across UI, API, database, and tests. Identify the specialized skill for each phase and define completion checks.
```

### Modernize a legacy application

```
Create a phased modernization plan for [application]. Cover architecture, migration risks, testing, security review, deployment, and rollback validation.
```

### Design a production delivery plan

```
Coordinate delivery for [system] with [constraints]. Define architecture decisions, dependencies, quality gates, CI/CD stages, security checks, observability, and release criteria.
```

## Limitations

- Coordinates other named skills but does not include their implementation details.
- Does not verify whether referenced skills are installed or available.
- Does not replace project-specific testing, security review, or deployment validation.
- Requires clear requirements, permissions, technology choices, and success criteria.

## Best Practices

- Confirm requirements, permissions, stack choices, and success criteria before selecting workflow phases.
- Complete each quality gate before moving to the next delivery phase.
- Validate generated work in the actual development, testing, and deployment environments.

## Anti Patterns

- Do not invoke every referenced skill when the task needs only a focused subset.
- Do not deploy generated changes without tests, security checks, and environment validation.
- Do not continue when requirements, permissions, or release criteria remain unclear.

## Security Audit

- Audited at: 2026-07-23T22:11:24.156\+00:00
- Summary: All 84 static findings are false positives caused by Markdown backticks used for code fences and inline skill names. SKILL.md contains workflow documentation and example prompts, with no executable shell or Ruby command path. No prompt injection or other semantic security issue was found.

## Stats

- Views: 100
- Downloads: 9
- Favorites: 0
- Popularity score: 0