skills.rest
Code for Philly avatar

Code for Philly

Official

@codeforphilly · Philadelphia, PA

0Followers
|
134Public Repos
|
3Published Skills

Philly's civic tech brigade

🐙 GitHub ↗🌐 Website ↗
Skills Distribution
DomainDeveloper To...Backend Architecture (40%)Frontend Engineering (40%)Specification Gove.. (20%)

Agent Skills by Code for Philly

Showing 3 vetted skills indexed across 1 GitHub repositories.

CodeForPhillyCodeForPhilly

backend-fastify

Standardize Fastify 5.x backend development with TypeScript and plugin architecture.

Official
Intermediate
CodeForPhillyCodeForPhilly

frontend-shadcn

Standardize React frontend development with Vite, React 19, TypeScript, Tailwind CSS, and React Router v7.

Official
Intermediate
CodeForPhillyCodeForPhilly

specops

Create and review YAML-based specs and plans for spec-driven development.

Official
Advanced

Frequently Asked Questions About Code for Philly

FAQPage Schema
What specific technical tasks are enabled by these civic tech standards?▼

These standards enable rapid deployment of modular backend services using Fastify 5.x and high-performance frontend interfaces via React 19 and Vite. They facilitate consistent codebases across civic projects by enforcing TypeScript integration, Tailwind CSS styling, and structured YAML-based specification reviews for all development phases.

Which engineering personas benefit from these standardized development patterns?▼

Full-stack engineers, civic technologists, and open-source contributors benefit from these patterns. The framework is designed for developers building municipal digital services who require consistent architectural foundations, standardized routing via React Router v7, and rigorous specification-driven development practices to ensure project maintainability and long-term scalability.

What are the primary prerequisites for implementing these development standards?▼

Implementation requires a foundational understanding of TypeScript, React 19, and Fastify 5.x. Developers must be prepared to adopt Vite for build processes and Tailwind CSS for styling. Additionally, teams must integrate YAML-based specification reviews into their development lifecycle to maintain compliance with the established project architecture.