Sports Media Inc. Computer Science Training Academy

Master Full-Stack & Cybersecurity with Claude Opus 4.7, GPT-5.5, Gemini 3.1 & Open Source Tools

Critical Policy: Project Execution and Requirements

Mandatory Project Initiation Requirements

No project begins until every prerequisite is satisfied.

No exceptions, no workarounds, no shortcuts.

Functionality First Policy

All teams must follow the correct development sequence:

1Build full working functionality end to end
2Confirm integrations, authentication, data flow, automation
3Only after it works, refine UI/UX and visual design

If UI/UX is built before functionality is complete, the project enters a burn cycle:

Wasted engineering hours
Constant redesign loops
Broken integrations
Delayed deployment
Unscalable execution

This is not acceptable in production organizations.

1. Prerequisites Checklist

PROJECT BLOCKED

0 of 10 prerequisites complete

ALL required before project start

No Project Begins Without ALL of the Following

Source department does not matter. Completion status does. No exceptions.

Quick Reference Project Start Checklist

□Business Plan Approved
□PRD Product Requirements Document
□BRD Business Requirements Document
□MVP Minimum Viable Product Specification
□20 Images Provided by CEO / Graphics / Assigned Department
□5 Videos Provided by CEO / Graphics / Assigned Department
□21st.dev Components Identified
□Tech Stack Confirmed
□OAuth Credentials Provisioned (Google, GitHub, Facebook if required)
□All API Keys Delivered and Verified

ALL BOXES CHECKED = PROJECT APPROVED

ANY BOX UNCHECKED = PROJECT BLOCKED

2. Credential Ownership Policy (Major Bottleneck Prevention)

Credential Ownership Policy

Most project delays are not caused by coding. They are caused by missing credentials and unclear ownership.

OAuth accounts and billing keys cannot be left to interns mid project.

The following must be provisioned by the CEO or assigned platform operator BEFORE development begins:

Google OAuth App Registration
GitHub OAuth App Registration
Stripe Live Payment Keys
Facebook Login OAuth (if applicable)
GoHighLevel API and Webhooks
Email Provider Credentials (SMTP, SendGrid, Mailgun)
Twilio SMS Credentials
Slack or Discord Integration Tokens
Any paid third party API access (ESPN, NewsAPI, AI platforms)

If these do not exist, the project is automatically blocked.

No development begins until credentials are provisioned and verified in a staging environment.

3. Cost of Non-Compliance

The Cost of Skipping Prerequisites

Per project without prerequisites: 50 hours wasted

Formula: (Projects) x 50 hrs = Total Hours Lost

Projects Done WrongHours WastedAt $50/hrAt $75/hr
1 project50 hours$2,500$3,750
5 projects250 hours$12,500$18,750
10 projects500 hours$25,000$37,500
25 projects1,250 hours$62,500$93,750

Execution without inputs destroys ROI.

Interactive Cost Calculator

Total Hours Wasted

50

Total Money Lost

$2,500

4. Standard Project Tech Stack

Standard Project Tech Stack

All web apps and software applications use the following baseline. Additional frameworks permitted only with CTO approval.

Core Framework

  • Next.jsv16+
  • Reactv19+
  • TypeScriptv5.7+

Styling

  • Tailwind CSSv3.4+
  • tailwind-merge / tailwindcss-animate
  • PostCSS / Autoprefixer

UI Components

  • Radix UI primitives
  • Headless UI
  • shadcn/ui patterns
  • cmdk command palette
  • Framer Motion animations
  • Sonner / react-hot-toast notifications

3D and Graphics (If Required)

  • Three.js with React Three Fiber
  • Drei utilities
  • React Spring animation support

Backend and Data Layer

  • Flexible based on project needs
  • No database system is assumed until MVP requires it

Validation and Data Fetching

  • Axios / SWR
  • Zod schema validation

AI Integration

  • Google GenAI SDK@google/genai

Hosting and Analytics

  • Vercel deployment
  • Speed Insights
  • Recharts visualization

Linting

  • ESLint with Next.js config

5. Mandatory UI/UX Quality Standards (21st.dev)

Mandatory UI/UX Quality Standards (21st.dev)

Every project must look like it was built by a Fortune 500 design team.

If a component looks like any of the following, it is rejected and rebuilt:

Generic Bootstrap
Default Material UI
Obvious AI generated UI
Low effort layouts

21st.dev is the required component standard for:

Hero sections
Dashboards
Pricing tables
Navigation systems
Forms and validation UX
Modals and dialogs
Loading and error states
Data display layouts

Company Access

Login MethodGitHub Authentication
Accountnft@mysportsmedia.net

All team members use this shared account for component access.

Workflow

Step 1

Identify UI component needed

Step 2

Search 21st.dev first

Step 3

Copy production ready component into project

Step 4

Customize branding and content

Step 5

Only build custom components if none exist

Last Updated: May 12, 2026

Sports Media Inc. Computer Science SOP

Project Requirements and Execution Policy