How mijeeapps-collab/it-skill-quiz works
1. Project shape
- This is a small, single-route Next.js App Router application.
- There are no visible API routes, server actions, database layers, or external service integrations in the tree, so the runtime architecture is primarily client-side UI state + local content.
2. Top-level entry points
- app/layout.tsx defines the shared document shell.
- app/page.tsx is the main application entry and likely contains the core state machine for the quiz flow.
- app/globals.css provides global styling across the app.
3. Main user flow
- The component set suggests a flow like: start screen → category selection → quiz questions → progress feedback → result screen.
- StartScreen, CategoryCard, QuizCard, ProgressBar, and ResultCard map directly to these stages.
4. UI subsystem
- components/ contains the presentational building blocks:
- StartScreen.tsx for the landing/entry state.
- CategoryCard.tsx for category choice or display.
- QuizCard.tsx for question rendering and answer interaction.
- ProgressBar.tsx for tracking progress through the quiz.
- ResultCard.tsx for final scoring or outcome display.
- This separation keeps screen composition in the page layer and display logic in reusable components.
5. State and orchestration boundary
- app/page.tsx is the likely orchestration layer that coordinates:
- current screen/state,
- selected category,
- current question index,
- accumulated score or completion result.
- In diagram terms, this is the main control node between static data and the UI components.
6. Data model
- types/question.ts defines the core domain types for the quiz data.
- This acts as the contract between content (data/questions.ts) and the rendering components, ensuring consistent question/category/result structures.
7. Content source
- data/questions.ts is the local content store for quiz questions.
- Because questions live in the repository rather than in a backend, the app is content-driven but offline/local-data based.
- The file tree suggests questions are grouped by category or similar metadata.
8. Styling and design system
- Styling is handled with standard Next.js CSS:
- app/globals.css for global rules,
- postcss.config.mjs for CSS processing.
- There is no dedicated CSS-in-JS or component library visible, so the visual layer is likely custom and lightweight.
9. Platform/runtime dependencies
- The stack is TypeScript + React + Next.js.
- package.json, tsconfig.json, eslint.config.mjs, and next.config.ts indicate a standard Next.js TypeScript setup with linting and build configuration.
- package-lock.json shows npm is the package manager in use.
10. Static assets and deployment
- public/ is the static asset boundary for images, icons, and other files served directly by Next.js.
- The README indicates default Vercel-compatible deployment, but nothing in the tree suggests custom infrastructure beyond standard Next.js hosting.
11. Documentation / stray artifacts
- README.md is the generic create-next-app scaffold, so it does not document domain behavior.
- 第一歩.txt and 第二歩.txt look like repository notes or draft content files; they are not part of the obvious app runtime path but may inform content or future development.
12. Architecture summary
- The repo is best diagrammed as: one Next.js page orchestrating a quiz experience, backed by local typed question data, and rendered through a small set of screen-specific UI components.
- The main boundary is between content/model (data/, types/) and presentation/control (app/, components/), with no backend boundary present.
Main entry points: page.tsx Quiz page · layout.tsx Layout · questions.ts Questions data · question.ts Question types
Components 16
App shell
Next.js App Router entry and global styling
- Layout · Shared document and app shell
app/layout.tsx - Quiz page · Main route that coordinates quiz state and screen transitions
app/page.tsx - Global CSS · App-wide styling rules
app/globals.css
UI flow
Screen components composing the quiz experience
- Start screen · Entry screen for beginning the quiz
components/StartScreen.tsx - Category card · Category choice or display component
components/CategoryCard.tsx - Quiz card · Renders questions and answer interaction
components/QuizCard.tsx - Progress bar · Shows quiz completion progress
components/ProgressBar.tsx - Result card · Displays final score or outcome
components/ResultCard.tsx
Content model
Typed local quiz data and domain contracts
- Questions data · Local quiz content grouped by category
data/questions.ts - Question types · Shared TypeScript contracts for quiz data
types/question.ts
Platform
Build, lint, and runtime configuration
- Next config · Next.js configuration
next.config.ts - PostCSS · CSS processing configuration
postcss.config.mjs - ESLint · Code quality rules
eslint.config.mjs - TS config · TypeScript project settings
tsconfig.json - Package manifest · Project dependencies and scripts
package.json - Public assets · Static files served directly by Next.js
public
Connections 19
- Layout → Quiz page: renders · Layout wraps the route content
- Quiz page → Start screen: entry state · Initial screen shown before the quiz begins
- Quiz page → Category card: selects category · Handles category choice and display
- Quiz page → Quiz card: drives quiz · Coordinates question display and answer flow
- Quiz page → Progress bar: tracks progress · Updates completion feedback during the quiz
- Quiz page → Result card: shows result · Presents the final outcome after completion
- Quiz page → Questions data: reads content · Uses local question bank as the quiz source
- Questions data → Question types: typed by · Question data conforms to shared domain types
- Quiz card → Question types: consumes types · Question rendering depends on the quiz schema
- Category card → Questions data: filters data · Category selection maps into grouped question content
- Start screen → Quiz page: starts flow · User action enters the orchestrated quiz state machine
- Result card → Quiz page: restarts flow · Outcome screen returns control to the page orchestrator
- Global CSS → Layout: applies to · Global styles are loaded through the app shell
- Next config → Quiz page: builds app · Next.js config supports the App Router runtime
- PostCSS → Global CSS: processes · PostCSS handles stylesheet processing
- Package manifest → Next config: configures · Project dependencies and scripts support the build setup
- ESLint → Quiz page: checks · Linting covers the application code
- TS config → Question types: compiles · TypeScript configuration governs shared types and app code
- Public assets → Layout: serves assets · Static files are available to the app shell