Build comprehensive 3-5 year financial models with revenue

Startup financial modeling

by wshobson · MIT license · ★ 39,857 on GitHub · v1.0.0 · updated Sep 21

Startup financial modeling cover

Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups. Use this skill when creating financial projections, calculating burn rate or…

---
name: startup-financial-modeling
description: Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups. Use this skill when creating financial projections, calculating burn rate or runway, modeling fundraising scenarios, or preparing investor-ready financials for a seed or Series A raise.
version: 1.0.0
---

# Startup Financial Modeling

Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.

## Overview

Financial modeling provides the quantitative foundation for startup strategy, fundraising, and operational planning. Create realistic projections using cohort-based revenue modeling, detailed cost structures, and scenario analysis to support decision-making and investor presentations.

## Core Components

### Revenue Model

Overview

Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.

Manual install (npx, ZIP)
Claude Codenpx skills add wshobson/agents --skill startup-financial-modeling -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wshobson/agents/tar.gz/4236bb91f839 \ | tar -xz -C ~/.claude/skills --strip-components=4 agents-4236bb91f839/plugins/startup-business-analyst/skills/startup-financial-modeling
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/ae2f91d4d9836bfaa461/startup-financial-modeling.zip" -OutFile "$env:TEMP\startup-financial-modeling.zip"; Expand-Archive "$env:TEMP\startup-financial-modeling.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.6 KB
  • references/1 file · 2.8 KB
Read the files here
wshobson/4236bb92 files
SKILL.md
Show the full text329 lines

Startup Financial Modeling

Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.

Overview

Financial modeling provides the quantitative foundation for startup strategy, fundraising, and operational planning. Create realistic projections using cohort-based revenue modeling, detailed cost structures, and scenario analysis to support decision-making and investor presentations.

Core Components

Revenue Model

Cohort-Based Projections: Build revenue from customer acquisition and retention by cohort.

Formula:

MRR = Σ (Cohort Size × Retention Rate × ARPU)
ARR = MRR × 12

Key Inputs:

  • Monthly new customer acquisitions
  • Customer retention rates by month
  • Average revenue per user (ARPU)
  • Pricing and packaging assumptions
  • Expansion revenue (upsells, cross-sells)
Cost Structure

Operating Expenses Categories:

  1. Cost of Goods Sold (COGS)

    • Hosting and infrastructure
    • Payment processing fees
    • Customer support (variable portion)
    • Third-party services per customer
  2. Sales & Marketing (S&M)

    • Customer acquisition cost (CAC)
    • Marketing programs and advertising
    • Sales team compensation
    • Marketing tools and software
  3. Research & Development (R&D)

    • Engineering team compensation
    • Product management
    • Design and UX
    • Development tools and infrastructure
  4. General & Administrative (G&A)

    • Executive team
    • Finance, legal, HR
    • Office and facilities
    • Insurance and compliance
Cash Flow Analysis

Components:

  • Beginning cash balance
  • Cash inflows (revenue, fundraising)
  • Cash outflows (operating expenses, CapEx)
  • Ending cash balance
  • Monthly burn rate
  • Runway (months of cash remaining)

Formula:

Runway = Current Cash Balance / Monthly Burn Rate
Monthly Burn = Monthly Revenue - Monthly Expenses
Headcount Planning

Role-Based Hiring Plan: Track headcount by department and role.

Key Metrics:

  • Fully-loaded cost per employee
  • Revenue per employee
  • Headcount by department (% of total)

Typical Ratios (Early-Stage SaaS):

  • Engineering: 40-50%
  • Sales & Marketing: 25-35%
  • G&A: 10-15%
  • Customer Success: 5-10%

Financial Model Structure

Three-Scenario Framework

Conservative Scenario (P10):

  • Slower customer acquisition
  • Lower pricing or conversion
  • Higher churn rates
  • Extended sales cycles
  • Used for cash management

Base Scenario (P50):

  • Most likely outcomes
  • Realistic assumptions
  • Primary planning scenario
  • Used for board reporting

Optimistic Scenario (P90):

  • Faster growth
  • Better unit economics
  • Lower churn
  • Used for upside planning
Time Horizon

Detailed Projections: 3 Years

  • Monthly detail for Year 1
  • Monthly detail for Year 2
  • Quarterly detail for Year 3

High-Level Projections: Years 4-5

  • Annual projections
  • Key metrics only
  • Support long-term planning

Detailed section: Step-by-Step Process

Originally a 2763-byte section in this SKILL.md. Moved to references/details.md to fit Codex's 8 KB skill body cap.

Business Model Templates

SaaS Financial Model

Revenue Drivers:

  • New MRR (customers × ARPU)
  • Expansion MRR (upsells)
  • Contraction MRR (downgrades)
  • Churned MRR (lost customers)

Key Ratios:

  • Gross margin: 75-85%
  • S&M as % revenue: 40-60% (early stage)
  • CAC payback: < 12 months
  • Net retention: 100-120%

Example Projection:

Year 1: $500K ARR, 50 customers, $100K MRR by Dec
Year 2: $2.5M ARR, 200 customers, $208K MRR by Dec
Year 3: $8M ARR, 600 customers, $667K MRR by Dec
Marketplace Financial Model

Revenue Drivers:

  • GMV (Gross Merchandise Value)
  • Take rate (% of GMV)
  • Net revenue = GMV × Take rate

Key Ratios:

  • Take rate: 10-30% depending on category
  • CAC for buyers vs. sellers
  • Contribution margin: 60-70%

Example Projection:

Year 1: $5M GMV, 15% take rate = $750K revenue
Year 2: $20M GMV, 15% take rate = $3M revenue
Year 3: $60M GMV, 15% take rate = $9M revenue
E-Commerce Financial Model

Revenue Drivers:

  • Traffic (visitors)
  • Conversion rate
  • Average order value (AOV)
  • Purchase frequency

Key Ratios:

  • Gross margin: 40-60%
  • Contribution margin: 20-35%
  • CAC payback: 3-6 months
Services / Agency Financial Model

Revenue Drivers:

  • Billable hours or projects
  • Hourly rate or project fee
  • Utilization rate
  • Team capacity

Key Ratios:

  • Gross margin: 50-70%
  • Utilization: 70-85%
  • Revenue per employee

Fundraising Integration

Funding Scenario Modeling

Pre-Money Valuation: Based on metrics and comparables.

Dilution:

Post-Money = Pre-Money + Investment
Dilution % = Investment / Post-Money

Use of Funds: Allocate funding to extend runway and achieve milestones.

Example:

Raise: $5M at $20M pre-money
Post-Money: $25M
Dilution: 20%

Use of Funds:
- Product Development: $2M (40%)
- Sales & Marketing: $2M (40%)
- G&A and Operations: $0.5M (10%)
- Working Capital: $0.5M (10%)
Milestone-Based Planning

Identify Key Milestones:

  • Product launch
  • First $1M ARR
  • Break-even on CAC
  • Series A fundraise

Funding Amount: Ensure runway to achieve next milestone + 6 months buffer.

Common Pitfalls

Pitfall 1: Overly Optimistic Revenue

  • New startups rarely hit aggressive projections
  • Use conservative customer acquisition assumptions
  • Model realistic churn rates

Pitfall 2: Underestimating Costs

  • Add 20% buffer to expense estimates
  • Include fully-loaded compensation
  • Account for software and tools

Pitfall 3: Ignoring Cash Flow Timing

  • Revenue ≠ cash (payment terms)
  • Expenses paid before revenue collected
  • Model cash conversion carefully

Pitfall 4: Static Headcount

  • Hiring takes time (3-6 months to fill roles)
  • Ramp time for productivity (3-6 months)
  • Account for attrition (10-15% annually)

Pitfall 5: Not Scenario Planning

  • Single scenario is never accurate
  • Always model conservative case
  • Plan for what you'll do if base case fails

Model Validation

Sanity Checks:

  • Revenue growth rate is achievable (3x in Year 2, 2x in Year 3)
  • Unit economics are realistic (LTV/CAC > 3, payback < 18 months)
  • Burn multiple is reasonable (< 2.0 in Year 2-3)
  • Headcount scales with revenue (revenue per employee growing)
  • Gross margin is appropriate for business model
  • S&M spending aligns with CAC and growth targets

Benchmark Against Peers: Compare key metrics to similar companies at similar stage.

Investor Feedback: Share model with advisors or investors for feedback on assumptions.

Quick Start

To create a startup financial model:

  1. Define business model - Revenue drivers and pricing
  2. Project revenue - Cohort-based with retention
  3. Model costs - COGS, S&M, R&D, G&A by month
  4. Plan headcount - Hiring by role and department
  5. Calculate cash flow - Revenue - expenses = burn/runway
  6. Compute metrics - CAC, LTV, burn multiple, runway
  7. Create scenarios - Conservative, base, optimistic
  8. Validate assumptions - Sanity check and benchmark
  9. Integrate fundraising - Model funding rounds and milestones
1---
2name: startup-financial-modeling
3description: Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups. Use this skill when creating financial projections, calculating burn rate or runway, modeling fundraising scenarios, or preparing investor-ready financials for a seed or Series A raise.
4version: 1.0.0
5---
6 
7# Startup Financial Modeling
8 
9Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.
10 
11## Overview
12 
13Financial modeling provides the quantitative foundation for startup strategy, fundraising, and operational planning. Create realistic projections using cohort-based revenue modeling, detailed cost structures, and scenario analysis to support decision-making and investor presentations.
14 
15## Core Components
16 
17### Revenue Model
18 
19**Cohort-Based Projections:**
20Build revenue from customer acquisition and retention by cohort.
21 
22**Formula:**
23 
24```
25MRR = Σ (Cohort Size × Retention Rate × ARPU)
26ARR = MRR × 12
27```
28 
29**Key Inputs:**
30 
31- Monthly new customer acquisitions
32- Customer retention rates by month
33- Average revenue per user (ARPU)
34- Pricing and packaging assumptions
35- Expansion revenue (upsells, cross-sells)
36 
37### Cost Structure
38 
39**Operating Expenses Categories:**
40 
411. **Cost of Goods Sold (COGS)**
42 - Hosting and infrastructure
43 - Payment processing fees
44 - Customer support (variable portion)
45 - Third-party services per customer
46 
472. **Sales & Marketing (S&M)**
48 - Customer acquisition cost (CAC)
49 - Marketing programs and advertising
50 - Sales team compensation
51 - Marketing tools and software
52 
533. **Research & Development (R&D)**
54 - Engineering team compensation
55 - Product management
56 - Design and UX
57 - Development tools and infrastructure
58 
594. **General & Administrative (G&A)**
60 - Executive team
61 - Finance, legal, HR
62 - Office and facilities
63 - Insurance and compliance
64 
65### Cash Flow Analysis
66 
67**Components:**
68 
69- Beginning cash balance
70- Cash inflows (revenue, fundraising)
71- Cash outflows (operating expenses, CapEx)
72- Ending cash balance
73- Monthly burn rate
74- Runway (months of cash remaining)
75 
76**Formula:**
77 
78```
79Runway = Current Cash Balance / Monthly Burn Rate
80Monthly Burn = Monthly Revenue - Monthly Expenses
81```
82 
83### Headcount Planning
84 
85**Role-Based Hiring Plan:**
86Track headcount by department and role.
87 
88**Key Metrics:**
89 
90- Fully-loaded cost per employee
91- Revenue per employee
92- Headcount by department (% of total)
93 
94**Typical Ratios (Early-Stage SaaS):**
95 
96- Engineering: 40-50%
97- Sales & Marketing: 25-35%
98- G&A: 10-15%
99- Customer Success: 5-10%
100 
101## Financial Model Structure
102 
103### Three-Scenario Framework
104 
105**Conservative Scenario (P10):**
106 
107- Slower customer acquisition
108- Lower pricing or conversion
109- Higher churn rates
110- Extended sales cycles
111- Used for cash management
112 
113**Base Scenario (P50):**
114 
115- Most likely outcomes
116- Realistic assumptions
117- Primary planning scenario
118- Used for board reporting
119 
120**Optimistic Scenario (P90):**
121 
122- Faster growth
123- Better unit economics
124- Lower churn
125- Used for upside planning
126 
127### Time Horizon
128 
129**Detailed Projections: 3 Years**
130 
131- Monthly detail for Year 1
132- Monthly detail for Year 2
133- Quarterly detail for Year 3
134 
135**High-Level Projections: Years 4-5**
136 
137- Annual projections
138- Key metrics only
139- Support long-term planning
140 
141## Detailed section: Step-by-Step Process
142 
143Originally a 2763-byte section in this SKILL.md. Moved to `references/details.md` to fit Codex's 8 KB skill body cap.
144 
145## Business Model Templates
146 
147### SaaS Financial Model
148 
149**Revenue Drivers:**
150 
151- New MRR (customers × ARPU)
152- Expansion MRR (upsells)
153- Contraction MRR (downgrades)
154- Churned MRR (lost customers)
155 
156**Key Ratios:**
157 
158- Gross margin: 75-85%
159- S&M as % revenue: 40-60% (early stage)
160- CAC payback: < 12 months
161- Net retention: 100-120%
162 
163**Example Projection:**
164 
165```
166Year 1: $500K ARR, 50 customers, $100K MRR by Dec
167Year 2: $2.5M ARR, 200 customers, $208K MRR by Dec
168Year 3: $8M ARR, 600 customers, $667K MRR by Dec
169```
170 
171### Marketplace Financial Model
172 
173**Revenue Drivers:**
174 
175- GMV (Gross Merchandise Value)
176- Take rate (% of GMV)
177- Net revenue = GMV × Take rate
178 
179**Key Ratios:**
180 
181- Take rate: 10-30% depending on category
182- CAC for buyers vs. sellers
183- Contribution margin: 60-70%
184 
185**Example Projection:**
186 
187```
188Year 1: $5M GMV, 15% take rate = $750K revenue
189Year 2: $20M GMV, 15% take rate = $3M revenue
190Year 3: $60M GMV, 15% take rate = $9M revenue
191```
192 
193### E-Commerce Financial Model
194 
195**Revenue Drivers:**
196 
197- Traffic (visitors)
198- Conversion rate
199- Average order value (AOV)
200- Purchase frequency
201 
202**Key Ratios:**
203 
204- Gross margin: 40-60%
205- Contribution margin: 20-35%
206- CAC payback: 3-6 months
207 
208### Services / Agency Financial Model
209 
210**Revenue Drivers:**
211 
212- Billable hours or projects
213- Hourly rate or project fee
214- Utilization rate
215- Team capacity
216 
217**Key Ratios:**
218 
219- Gross margin: 50-70%
220- Utilization: 70-85%
221- Revenue per employee
222 
223## Fundraising Integration
224 
225### Funding Scenario Modeling
226 
227**Pre-Money Valuation:**
228Based on metrics and comparables.
229 
230**Dilution:**
231 
232```
233Post-Money = Pre-Money + Investment
234Dilution % = Investment / Post-Money
235```
236 
237**Use of Funds:**
238Allocate funding to extend runway and achieve milestones.
239 
240**Example:**
241 
242```
243Raise: $5M at $20M pre-money
244Post-Money: $25M
245Dilution: 20%
246 
247Use of Funds:
248- Product Development: $2M (40%)
249- Sales & Marketing: $2M (40%)
250- G&A and Operations: $0.5M (10%)
251- Working Capital: $0.5M (10%)
252```
253 
254### Milestone-Based Planning
255 
256**Identify Key Milestones:**
257 
258- Product launch
259- First $1M ARR
260- Break-even on CAC
261- Series A fundraise
262 
263**Funding Amount:**
264Ensure runway to achieve next milestone + 6 months buffer.
265 
266## Common Pitfalls
267 
268**Pitfall 1: Overly Optimistic Revenue**
269 
270- New startups rarely hit aggressive projections
271- Use conservative customer acquisition assumptions
272- Model realistic churn rates
273 
274**Pitfall 2: Underestimating Costs**
275 
276- Add 20% buffer to expense estimates
277- Include fully-loaded compensation
278- Account for software and tools
279 
280**Pitfall 3: Ignoring Cash Flow Timing**
281 
282- Revenue ≠ cash (payment terms)
283- Expenses paid before revenue collected
284- Model cash conversion carefully
285 
286**Pitfall 4: Static Headcount**
287 
288- Hiring takes time (3-6 months to fill roles)
289- Ramp time for productivity (3-6 months)
290- Account for attrition (10-15% annually)
291 
292**Pitfall 5: Not Scenario Planning**
293 
294- Single scenario is never accurate
295- Always model conservative case
296- Plan for what you'll do if base case fails
297 
298## Model Validation
299 
300**Sanity Checks:**
301 
302- [ ] Revenue growth rate is achievable (3x in Year 2, 2x in Year 3)
303- [ ] Unit economics are realistic (LTV/CAC > 3, payback < 18 months)
304- [ ] Burn multiple is reasonable (< 2.0 in Year 2-3)
305- [ ] Headcount scales with revenue (revenue per employee growing)
306- [ ] Gross margin is appropriate for business model
307- [ ] S&M spending aligns with CAC and growth targets
308 
309**Benchmark Against Peers:**
310Compare key metrics to similar companies at similar stage.
311 
312**Investor Feedback:**
313Share model with advisors or investors for feedback on assumptions.
314 
315 
316## Quick Start
317 
318To create a startup financial model:
319 
3201. **Define business model** - Revenue drivers and pricing
3212. **Project revenue** - Cohort-based with retention
3223. **Model costs** - COGS, S&M, R&D, G&A by month
3234. **Plan headcount** - Hiring by role and department
3245. **Calculate cash flow** - Revenue - expenses = burn/runway
3256. **Compute metrics** - CAC, LTV, burn multiple, runway
3267. **Create scenarios** - Conservative, base, optimistic
3278. **Validate assumptions** - Sanity check and benchmark
3289. **Integrate fundraising** - Model funding rounds and milestones
329 
View all files on GitHub →

Details

Version
1.0.0
Updated
Sep 21, 2026
License
MIT
Stars on the repo
★ 39,857
Checked
Source
wshobson/agents ↗
Creator
wshobson · 179 listings
View creator

Similar skills

See all →
SkillAnalyze ad campaign performance data to identify what'sAd campaign analyzergooseworks-ai/goose-skills · by gooseworks-aiAnalyze ad campaign performance data (Google, Meta, LinkedIn) to identify what's working, what's wasting budget, and specific cut/scale/test recommendations. Runs statistical analysis, funnel diagnostics, and multi-channel budget reallocation with specific dollar-amount shift recommendations and scenario modeling.★ 1.2k GitHub starsSkillYour CFOFounder cfoJakeschincariol/founder-skill · by JakeschincariolYour CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers", "is this profitable", "break-even", "unit economics", "how much do I need to start", or "run the CFO".★ 322 GitHub starsMCPYou need to establish project plansProject managerdavila7/claude-code-templates · by davila7Use this agent when you need to establish project plans, track execution progress, manage risks, control budget/schedule, and coordinate stakeholders across complex initiatives. Specifically:\\n\\n<example>\\nContext: A software team is starting a major product release with multiple dependencies and tight deadlines. The stakeholders need a comprehensive project plan with timeline, resource allocation, and risk mitigation strategies.\\nuser: "We're launching a new payment processing platform in Q2. Can you help us plan the project, identify risks, and set up tracking?"\\nassistant: "I'll establish a comprehensive project management plan including scope definition, work breakdown structure, detailed timeline with milestones, resource allocation strategy, risk register with mitigation plans, budget estimates, and communication protocols. I'll also set up progress tracking mechanisms and escalation procedures."\\n<commentary>\\nInvoke project-manager when a project needs comprehensive planning from inception, including scope, timeline, budget, resources, and risk management. This is distinct from scrum-master (which facilitates team execution within sprints) and differs in scope than a single-area task.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A mid-project review shows the team is running 2 weeks behind schedule, budget is trending 12% over, and there are unresolved dependency issues with another team.\\nuser: "Our project is sliding. We're behind schedule, over budget, and stuck waiting on another team. I need to understand what's happening and how to fix it."\\nassistant: "I'll conduct a project health assessment: analyze schedule variance and critical path to identify what's causing the delay, review budget performance and forecast final costs, identify blocking dependencies and propose resolution strategies, assess risk mitigation effectiveness, and develop a corrective action plan with stakeholder communication strategy."\\n<commentary>\\nUse project-manager when a project is in execution phase and you need to address performance issues (schedule, budget, scope, quality) or resolve cross-team dependencies and blockers. Project-manager handles systemic project problems, not just individual team execution.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A project is nearing completion with deliverables ready for handoff. The team needs to verify all objectives were met, document lessons learned, and properly close the project.\\nuser: "We're wrapping up the mobile app redesign. Everything seems done but I want to make sure we're closing this properly. Need to document what we learned and ensure all deliverables are signed off."\\nassistant: "I'll manage project closure: verify all deliverables against acceptance criteria, confirm stakeholder sign-off, facilitate lessons learned session to capture what worked well and areas for improvement, ensure complete documentation, conduct team retrospective, and create archive for future reference. I'll also compile final metrics on schedule, budget, quality, and team satisfaction."\\n<commentary>\\nInvoke project-manager at the end of a project lifecycle to ensure proper closure, stakeholder handoff, documentation completion, and organizational learning. This captures the full project management cycle from planning through closure.\\n</commentary>\\n</example>★ 32.3k GitHub starsSkill/cs:cfo-review <plan/cs:cfo-review — CFO Forcing Questionsalirezarezvani/claude-skills · by alirezarezvani/cs:cfo-review <plan> — Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation. Use when a plan commits meaningful spend — e.g. a hiring wave, a fundraise decision, or a new channel budget.★ 26.3k GitHub starsSkill/cs:founder-mode <question/cs:founder-mode — The Auto-Routeralirezarezvani/claude-skills · by alirezarezvani/cs:founder-mode <question> — Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits — e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO.★ 26.3k GitHub starsSkillBusiness investment analysis and capital allocation advisorBusiness investment advisoralirezarezvani/claude-skills · by alirezarezvaniBusiness investment analysis and capital allocation advisor. Use when evaluating whether to invest in equipment, real estate, a new business, hiring, technology, or any capital expenditure. Also use for ROI calculations, IRR, NPV, payback period, build vs buy decisions, lease vs buy analysis, vendor evaluation, or deciding where to allocate limited budget for maximum return.★ 26.3k GitHub stars

More from wshobson

SkillMaster C/.NET backend development patterns for buildingwshobson/agents · by wshobsonMaster C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.★ 39.9k GitHub starsSkillImplement WCAG 2.2 compliant interfaces with mobileAccessibility compliancewshobson/agents · by wshobsonImplement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.★ 39.9k GitHub starsSkillMaster Material Design 3 and Jetpack Compose patternsAndroid Mobile Designwshobson/agents · by wshobsonMaster Material Design 3 and Jetpack Compose patterns for building native Android apps. Use when designing Android interfaces, implementing Compose UI, or following Google's Material Design guidelines.★ 39.9k GitHub starsSkillMigrate from AngularJS to Angular using hybrid modeAngular migrationwshobson/agents · by wshobsonMigrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.★ 39.9k GitHub starsSkillUnderstand anti-reversing, obfuscationAnti reversing techniqueswshobson/agents · by wshobsonUnderstand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.★ 39.9k GitHub starsSkillBuild production Apache Airflow DAGs with best practicesApache Airflow DAG Patternswshobson/agents · by wshobsonBuild production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.★ 39.9k GitHub stars