SportCent
> Starter template for a monolith project. > Copy this file, fill in every [PLACEHOLDER], and rename it CODING_GUIDELINES.md. > Sections marked with ⚠️ are non-negotiable. ---
Install / Use
npx skills add FreeFurio/SportCentInstalls into whichever agent you are using.
Amazon Q Rules
Amazon Q Developer rules
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of SportCent
SportCent scores 70/100 on our quality scale, 3877th of 4,698 Development & Engineering skills we index.
Its Amazon Q Rules is 20 KB long, well organised into 71 sections with 16 code examples: a thorough specification that gives an agent plenty to work with.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-11-12 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-11. Automated pattern scan on 2026-11-11. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
SportCent compared with similar skills
All 4 of these similar skills score higher than SportCent; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| SportCent (this skill)by FreeFurio | 70 | 0 | — | Amazon Q Rules |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install SportCent?
- Run
npx skills add FreeFurio/SportCent. The install tabs above show the steps for each supported agent. - Which AI agents does SportCent work with?
- It is written for Amazon Q, as a Amazon Q Rules file. Other agents that read the same format can often use it too.
- Is SportCent safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is SportCent still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubCODING_GUIDELINES_MONOLITH.md
Starter template for a monolith project. Copy this file, fill in every [PLACEHOLDER], and rename it CODING_GUIDELINES.md. Sections marked with ⚠️ are non-negotiable.
0. Build Progress
Infrastructure
- [ ] Single GitHub repo created
- [ ] Nginx config + SSL setup
- [ ] Docker Compose wiring app + DB + Redis
- [ ] Grafana + Prometheus + Loki running
- [ ] Playwright E2E test suite scaffolded
- [ ] k6 load test suite scaffolded
- [ ] Runbooks written for all critical alerts
- [ ] Production VM provisioned
- [ ] Object storage bucket created
- [ ] CDN configured
- [ ] WAF enabled
- [ ] Firewall — only CDN IPs allowed inbound
Backend — [project]-api
- [ ] Project scaffolded (package.json, ES Modules, Express)
- [ ] Env var validation on startup
- [ ] JWT auth middleware
- [ ] Rate limiting middleware (Redis)
- [ ] Request validation middleware (Zod)
- [ ] Response normalization middleware
- [ ] Feature flags (DB table + admin toggle)
- [ ] Graceful shutdown
- [ ] GET /health endpoint
- [ ] Structured logging (Pino)
- [ ] OpenTelemetry instrumentation
- [ ] Dockerfile + docker-compose.yml
- [ ] GitHub Actions deploy.yml
- [ ] .env.example
- [ ] Unit tests
- [ ] Integration tests
Frontend — [project]-web
- [ ] Project scaffolded (React 18 + Vite 5)
- [ ] Single Axios API client configured
- [ ] Auth — login, register, token refresh
- [ ] Route guards ([Role1] vs [Role2])
- [ ] [Core pages — list them]
- [ ] SSE connection — live updates (if needed)
- [ ] [Role2] admin pages
- [ ] Admin — analytics dashboard
- [ ] Admin — feature flag toggle
- [ ] Every interactive element has data-testid
- [ ] All views handle loading, empty, error states
- [ ] Mobile-first responsive layout (360px+)
- [ ] DOMPurify on any user-generated HTML render
- [ ] Dockerfile + Nginx static serving
- [ ] GitHub Actions deploy.yml
- [ ] .env.example
0.1. AI Workflow ⚠️ FOLLOW STRICTLY AND EVERY TIME
- Read CODING_GUIDELINES.md first — always, before anything else, on every request.
- Read every file related to the request before answering. Re-read each time; do not rely on earlier messages.
- If the request is unclear or ambiguous, ask before doing anything. Never assume.
- Restate the request in your own words so it can be confirmed.
- Give suggestions first. Wait until "go" before giving any code.
- Multiple files: go in sequence — finish one file before moving to the next.
- Every code block shows Before and After.
- Only change files directly related to the request. Never touch unrelated files.
- When "done" is said, check the files again and confirm there are no errors.
- If a question is skipped or missed, ask it again. Never decide alone.
- Be consistent with the existing coding pattern.
1. Project
Project Name: [ProjectName]
Stack: Node.js + Express, React + Vite, PostgreSQL
Language: JavaScript (ES Modules)
Roles: [Role1], [Role2]
Architecture: Monolith — single repo, single deployable backend
Local Dev: Docker Compose (one docker-compose.yml at repo root)
Production: [Cloud VM] — Docker Compose
CI/CD: GitHub Actions → GitHub Container Registry → [Cloud VM]
Mobile (future): React Native — API stays REST, no changes needed
Modules (features inside the monolith)
| Module | Responsibility | |---|---| | auth | Registration, login, JWT issuing + refresh, roles | | [domain-module-1] | [Responsibility] | | [domain-module-2] | [Responsibility] | | notifications | Email confirmations, reminders, alerts | | analytics | Counts, utilization, retention metrics |
Roles
| Role | What they can do | |---|---| | [Role1] | [Permissions] | | [Role2] | [Permissions] |
2. Tools & Technologies
| Tool | Version | Purpose | |---|---|---| | Node.js | 22 LTS | Runtime | | Express | 4.x | HTTP framework | | React | 18.x | Frontend | | Vite | 5.x | Frontend build tool | | PostgreSQL | 16 | Primary database | | Prisma | 5.x | ORM, migrations | | Redis | 7.x | Caching, rate limiting, BullMQ storage | | BullMQ | 4.x | Background job queues | | Vitest | latest | Unit and integration tests | | Supertest | latest | HTTP endpoint testing | | Playwright | latest | E2E browser tests | | k6 | latest | Load testing | | Docker | latest | Containerize the app | | Docker Compose | 2.x | Run app locally and on VM | | Nginx | latest | Reverse proxy, SSL termination | | GitHub Actions | — | CI/CD | | GitHub Container Registry | — | Docker image storage | | OpenTelemetry | latest | Instrumentation | | Pino | latest | Structured JSON logging | | Prometheus | latest | Metrics storage | | Loki | latest | Log storage | | Grafana | latest | Dashboards and alerting | | Zod | 3.x | Request validation | | DOMPurify | 3.x | Sanitize user-generated HTML | | Axios | 1.x | HTTP client (frontend) | | pg_basebackup | built-in | PostgreSQL backups | | [Cloud VM] | [tier] | Production server | | [Object Storage] | [tier] | File uploads — S3-compatible | | [CDN] | [tier] | Static file serving |
3. Database
Single Database
One PostgreSQL database for the entire application. Modules share the same DB instance but own their own tables — no module queries another module's tables directly. Go through the module's service layer instead.
Replication
- One PRIMARY + one REPLICA
- PRIMARY: all writes + reads where stale data causes wrong decisions
- REPLICA: non-critical reads where slight delay is acceptable
"Would a 50ms stale read cause a wrong decision?"
YES → PRIMARY
NO → REPLICA
PRIMARY reads: [list — e.g. inventory counts, payment status, record status] REPLICA reads: [list — e.g. listings, history, analytics, profile display]
Connection Pooling
Tool: PgBouncer or Prisma built-in pool
| Pool Size | Value | |---|---| | Total connections | [N] (stay under max_connections 100) |
Indexing
- Index every column used in WHERE, ORDER BY, or joins
- Index every foreign key
- Never over-index — every index slows writes
- Add indexes based on actual slow queries
Transactions
- Wrap multi-write workflows in a single DB transaction
- Transactions belong in the service layer
- Never make HTTP calls inside a transaction
- Use Prisma $transaction() for multi-step writes
Backups
- Full backup every 24 hours at midnight via pg_basebackup
- WAL logs (PITR) continuous
- Stored offsite — never on the same VM
- Keep last 7 days
- Test restoring regularly
Audit Trail
Status history table per entity:
[entity]_status_history
├── id
├── [entity]_id
├── old_status
├── new_status
├── changed_by
├── changed_at
└── reason
Migrations
- Prisma — one migrations folder at repo root
- Never edit the DB by hand
- Never edit an existing migration — create a new one
- Always backward compatible — two-step deploys for column changes
4. Architecture
- Single deployable — one Node.js process, one DB, one repo
- Modular internally — code is split by feature module, not by deployment unit
- No inter-module HTTP calls — modules call each other's service functions directly
- Background work — BullMQ jobs for async tasks (emails, cleanup, snapshots)
- Auth — JWT middleware on Express, verified on every protected route
- API — REST, versioned from day one (/api/v1/...)
- Consistency — DB transactions for multi-step writes, pessimistic locking for concurrent writes
When to extract a module into a separate service
Only extract when:
- The module has genuinely different scaling needs than the rest of the app
- The module needs to be deployed independently on a different schedule
- The team working on it is large enough to own a separate repo and pipeline
Do not extract early. A well-structured monolith is easier to operate than premature microservices.
Locking
| Situation | Type | Reason | |---|---|---| | [High-contention write] | Pessimistic (SELECT FOR UPDATE) | Conflicts are frequent | | [Admin edit] | Optimistic (version column) | Conflicts are rare |
5. Infrastructure
- Redis — caching, rate limiting, BullMQ storage
- BullMQ — background jobs on Redis
- SSE — server → client live updates (one way, if needed)
- Nginx — reverse proxy, SSL termination, static files
- Let's Encrypt — SSL, auto-renewed every 90 days
- [Cloud VM] — production server
- [Object Storage] — S3-compatible file storage
- [CDN] — serves files from object storage, caches at edge
Network Layout
Internet
↓
[Cloud VM] — port 443 only
↓
Nginx
↓
Express app :3000
↓
PostgreSQL + Redis (internal only)
docker-compose.yml (root)
services:
app ← Express backend
web ← React frontend (or served by Nginx)
db ← PostgreSQL
redis ← Redis
nginx ← reverse proxy
6. Auth
- JWT middleware on every protected route
- Identity module issues access token (15min) + refresh token (7 days)
- Verify token signature locally on every request — no DB call per request
- Token contains: userId, role, expiry
- Invalid token → 401 immediately
JWT Rotation
- Never swap JWT secret instantly — all sessions invalidated
- Dual secret: accept old + new for 24h, then drop old
7. Background Jobs (BullMQ)
| Job | Trigger | Action | |---|---|---| | send.reminder | [N] hours before event | Send reminder email | | expire.pending.[entity] | [N] min after creation | Cancel unconfirmed record | | generate.analytics.snapshot | Every midnight | Daily analytics | | cleanup.expired.data | Every night 3am | Soft + hard delete expired records |
Worker Concurrency
| Worker | Concurrency | |---|---| | Email/notification | 5 (email calls are slow) | | Analytics | 10 (fast DB writes) | | [Domain] | [N] |
Always set removeOnComplete: 100 and removeOnFail: 50 on every job.
8. Caching (Redis)
| Data | TTL | Never cache | |---|---|---| | [Public listings] | 5 min | [Critical status fields] | | [Config data] | 10 min | User-specific state | | [Aggregated stats] | 1 hour | JWT tokens |
9. Rate Limiting (Redis)
| Endpoint | Limit | |---|---| | POST /auth/login | 5 per minute | | POST /auth/register | 3 per minute | | POST /[resource] | 10 per minute | | GET /[listings] | 60 per minute |
10. File Storage
Upload Flow
Client → Server (validate type + size) → Server generates presigned URL (5 min)
Client uploads directly to [Object Storage]
Client sends URL back → Server saves CDN URL to DB
- Always store CDN URL in DB, never raw storage URL
- Validate file type and size on server before generating presigned URL
- Delete files via BullMQ job — never block the request
Allowed types: image/jpeg, image/png, image/webp — Max: 5MB
11. Real-Time (if needed)
| Feature | Tool | Direction | |---|---|---| | [Live status updates] | SSE | Server → client |
SSE requires sticky sessions when load balancing.
12. Resilience
Timeouts (outgoing HTTP to external APIs)
| Call | Timeout | |---|---| | [External API 1] | 5s | | [External API 2] | 10s |
Retries (external calls only)
- Retry on network errors or 5xx only — never on 4xx
- Max 3 retries: wait 1s → 2s → 4s
13. Testing
Pyramid
E2E (Playwright) — critical journeys only
Integration (Vitest + Supertest) — per endpoint
Unit (Vitest) — business logic only
No contract tests — there is only one deployable, no service boundaries to contract-test.
Unit Tests
- Pure logic only — no DB, no HTTP
- Only test services — not controllers, not repositories
- File: [feature].service.test.js
Integration Tests
- Full endpoint: HTTP → controller → service → real test DB
- Clean DB with beforeEach
- Test: happy path, 400, 403, 404, 409, concurrent requests
E2E Tests (Playwright)
- data-testid on every interactive element — never CSS or text selectors
- Lives in e2e/ at repo root
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
