web-application-developer
/web-application-developer
Guides web application development—browser-based products spanning UI, HTTP APIs, sessions and cookies, routing (SPA and SSR), forms, file uploads, and web-specific security (CSRF, CORS, CSP, XSS prevention) on stacks such as React/Next.js, Vue, or similar with Node/Python/Ruby backends. Use when building or maintaining a web app, implementing login flows, server-rendered or hybrid pages, REST/GraphQL consumption, or debugging browser–server issues—not for mobile native apps, CLI tools, or data pipelines. For generic full-stack feature delivery use fullstack-software-engineer; for front-end-on
- Author
- rade-nugroho ↗
- Repository
- agentic-enteprises-skill ↗
- Licence
- MIT
- Last repository change
- 20.05.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guides web application development—browser-based products spanning UI, HTTP APIs, sessions and cookies, routing (SPA and SSR), forms, file uploads, and web-specific security (CSRF, CORS, CSP, XSS prevention) on stacks such as React/Next.js, Vue, or similar with Node/Python/Ruby backends. Use when building or maintaining a web app, implementing login flows, server-rendered or hybrid pages, REST/GraphQL consumption, or debugging browser–server issues—not for mobile native apps, CLI tools, or data pipelines. For generic full-stack feature delivery use fullstack-software-engineer; for front-end-on
Original author description
Guides web application development—browser-based products spanning UI, HTTP APIs, sessions and cookies, routing (SPA and SSR), forms, file uploads, and web-specific security (CSRF, CORS, CSP, XSS prevention) on stacks such as React/Next.js, Vue, or similar with Node/Python/Ruby backends. Use when building or maintaining a web app, implementing login flows, server-rendered or hybrid pages, REST/GraphQL consumption, or debugging browser–server issues—not for mobile native apps, CLI tools, or data pipelines. For generic full-stack feature delivery use fullstack-software-engineer; for front-end-on
How it works
- When to Use
- When NOT to Use
- Related skills
- Core Workflows
- When to load references
SKILL.md preview
--- name: web-application-developer description: | Guides web application development—browser-based products spanning UI, HTTP APIs, sessions and cookies, routing (SPA and SSR), forms, file uploads, and web-specific security (CSRF, CORS, CSP, XSS prevention) on stacks such as React/Next.js, Vue, or similar with Node/Python/Ruby backends. Use when building or maintaining a web app, implementing login flows, server-rendered or hybrid pages, REST/GraphQL consumption, or debugging browser–server issues—not for mobile native apps, CLI tools, or data pipelines. For generic full-stack feature delivery use fullstack-software-engineer; for front-end-only work use senior-frontend-software-engineer; for deploy/CI use devops. For design-to-code UI implementation (tokens, states, Storybook) without auth/CORS focus, use ui-software-engineer. --- # Web Application Developer ## When to Use - Build or extend a browser-based web application (not native mobile) - Implement auth flows, sessions, or token handling in a web context - Connect UI to HTTP APIs with correct error and loading handling - Address CORS, cookies, CSRF, or caching behavior between browser and server - Ship SSR, SPA, or hybrid (e.g., Next.js) routing and data loading ## When NOT to Use - Native iOS/Android or desktop-only clients → stack-specific mobile/desktop guidance - Pure infrastructure or pipelines → `devops`, `infrastructure-engineer` - UX discovery and wireframes only → `product-designer` - Org-wide security program → `cybersecurity` - Senior cross-service RFCs → `senior-software-engineer` ## Related skills | Need | Skill | |---|---| | Full-stack IC features (general) | `fullstack-software-engineer` | | Senior full-stack delivery | `senior-fullstack-developer` | | Front-end architecture only | `senior-frontend-software-engineer` | | UI screens from design specs | `ui-software-engineer` | | UX specs and flows | `product-designer` | | Pipeline and hosting | `devops` | | Pipeline security scans | `devsecops` | ## Core Workflows ### 1. Web app structure Choose rendering model explicitly: | Model | When | |---|---| | SSR / hybrid | SEO, fast first paint, authenticated dashboards | | SPA | Heavy client interactivity, app behind login | | Static + API | Marketing site + separate app subdomain | Document: routes, auth gates, global layout, error boundaries. **See `references/web_app_architecture.md` for routing and env patterns.** ### 2. HTTP API integration - Use typed client or OpenAPI-generated types - Handle 401 → refresh or redirect to login - Timeouts and retry only for idempotent GETs - Paginate list endpoints; avoid loading unbounded data in browser **See `references/api_integration.md` for client patterns.** ### 3. Auth in the browser - Prefer HttpOnly, Secure, SameSite cookies for session cookies - Or short-lived access token in memory + refresh rotation - Never store secrets in localStorage for high-risk apps - Protect state-changing routes with CSRF tokens when using cookies **See `references/auth_sessions.md` for flow diagrams.** ### 4. Forms and uploads - Client validation for UX; server validation required - `multipart/form-data` for files; progress and size limits - Sanitize filenames; scan server-side if policy requires ### 5. Web security baseline - Escape output; avoid `dangerouslySetInnerHTML` without sanitizer - Set CSP headers; restrict script sources - CORS allowlist explicit origins—not `*` with credentials - Security headers: HSTS, X-Frame-Options or frame-ancestors **See `references/web_security.md` for checklist.** ### 6. Test and release - Unit: validators, hooks, API mappers - Integration: API routes with test DB - E2E: login and one critical journey (Playwright/Cypress) - Smoke test after deploy on staging URL **See `references/web_app_architecture.md` for env and config.** ## When to load references - **Architecture and env** → `references/web_app_architecture.md` - **API clients** → `references/api_integration.md` - **Login and sessions** → `references/auth_sessions.md` - **CSRF, CSP, CORS** → `references/web_security.md`
Files in this package (5)
- SKILL.md 4 KB
- references/api_integration.md 1 KB
- references/auth_sessions.md 1 KB
- references/web_app_architecture.md 1 KB
- references/web_security.md 1 KB
Versions
The database has no other skills named web-application-developer.
Database snapshot: 13.11.2026 · package version f5ddba5c068b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100secure-web
Secure patterns for web apps and APIs. Use when building or editing routes/endpoints/controllers, REST or GraphQL APIs, login/signup/password reset/OAuth/sessions/JWT, forms, file uploads, webhooks, payments/checkout/coupons, admin panels, multi-tenant data access,… - 90fullstack-software-engineer
Guides full-stack software engineering—end-to-end product features across web frontends (React/Next.js or similar), backend APIs (Node/TypeScript or Python), databases, auth, testing, and production debugging for maintainable application code. Use when building or fixing… - 90senior-fullstack-developer
Guides senior full-stack delivery across TypeScript/React/Next.js frontends, Node or Python APIs, relational databases, authentication, testing, performance, and pragmatic system design for product features. Use when implementing end-to-end features, designing REST/GraphQL… - 90security-browser-and-origin
Review browser security boundaries, CSP, cookies, CORS, CSRF, framing, and third-party scripts. Use when browser origin protections are implicated. - 90Full Stack Developer
Use for end-to-end web application work - REST or GraphQL API design, database schema and migrations, authentication and authorization, frontend component architecture and state management, forms and validation, caching, background jobs, and connecting the browser to the server.… - 100web-input-security
Secure the browser-facing surface: XSS, CSRF, file uploads, security headers, cookie flags, sensitive browser storage and open redirects. Use when building or auditing pages, forms, uploads, cookies or redirect logic.