Design Portfolio

🚀 Getting Started with Scratch

Scratch is a free, browser-based tool for making games. No downloads needed!

Go to scratch.mit.edu in your browser
Click “Join Scratch” to create a free account (or sign in if you have one)
Click “Create” to start a new project
You will see the Stage (where your game plays), the Sprite list (your characters/objects), and the Code area (where you drag blocks)

Need help? Scratch has built-in tutorials. Click the Tutorials button (top of the editor) and try “Make a Game” or “Make a Chase Game” to learn the basics quickly.

What is a Statement of Intent? It explains the PURPOSE of your game — what type of game it is, who it’s for, and what the player does. Think of it as your “game pitch” — how would you describe your game to a friend?

1.1 — Game Name

What is the name of your game? Choose something fun and memorable.

1.2 — Statement of Intent

Explain your game idea. Don't overthink it — just describe what the player does and why it's fun!

🌱 Fill in the blanks

• My game is called _____ and it is a _____ game.
• In this game, the player uses the _____ keys to _____.
• The goal is to _____ while avoiding _____.
• This game is designed for _____ (age group / type of player).
• I want players to feel _____ when they play.

1.3 — Target Audience

Who would play your game? Think about their age and what kinds of games they like.

🌱 Example answer

“My target audience is students aged 10–14 who enjoy quick, casual games they can play during a break. They like games that are easy to learn but get harder as you play, like Flappy Bird or Crossy Road.”

1.4 — Research: Existing Games

Find 2 games that are similar to your idea. They can be Scratch games (explore scratch.mit.edu), mobile games, or classic games. Take a screenshot of each and describe what’s good and what could be better.

Where to find games to research:
• Scratch: Go to scratch.mit.edu → Explore → Games
• Mobile/browser games: Think of games you already play!
• Take a screenshot by pressing PrtSc (Windows) or Cmd+Shift+4 (Mac)

Game 1

📷 Upload screenshot of Game 1

Game 2

📷 Upload screenshot of Game 2

1.5 — PMI Analysis of Your Favourite Game

Pick your favourite game from above. What’s good about it? What’s bad? What’s interesting?

➕ Plus (what’s good)

➖ Minus (what’s bad)

❓ Interesting

1.6 — Key Features List

List what your game will have. Think about the different “screens” or states (start, playing, game over) and what happens in each.

Feature / Screen	What It Does	Why Players Need It

Game Design Document (GDD) is your game’s blueprint. Before you start coding in Scratch, plan out what your game will do. This makes building it much easier!

2.1 — Game Design Document

Answer each question to plan your game. Be as specific as you can!

Game Type

🌱 Choose one (or combine!)

Maze game Chase game Platformer Catching game Dodging game Shooting game Quiz game Clicker game

What does the player DO? (core mechanic)

🌱 Examples

• “The player moves a basket left and right to catch falling fruit”
• “The player guides a character through a maze to reach the exit”
• “The player dodges falling obstacles while collecting power-ups”

Controls

How do you WIN? How do you LOSE?

Game Stages (describe what happens in each part of the game)

🌱 Fill this in

Start: When the green flag is clicked, the game shows...
Gameplay: The player is in a _____ and needs to _____...
Difficulty: The game gets harder by...
Game Over: When the player loses, the game shows...

2.2 — Mind Map / Brainstorm

Draw a mind map exploring your game ideas. Put your game name in the centre, then branch out: characters, enemies, power-ups, levels, sounds, colours. Draw on paper and photograph it.

📷 Upload mind map / brainstorm image

2.3 — Rough Sketches of Game Screens

Draw what your game will look like at each stage. Show where the player, enemies, score, and other objects will be on screen. Use boxes for buttons, stick figures for characters. Label everything!

Tip: In Scratch, your game happens on a 480 x 360 pixel stage. Think about what sprites are on screen and where they are positioned. Draw a rectangle for the stage and sketch what goes inside it.

Screen 1: Start / Title

📷 Upload sketch

Screen 2: Gameplay

📷 Upload sketch

Screen 3: Game Over

📷 Upload sketch

Screen 4 (optional)

📷 Upload sketch

2.4 — Player Flow Diagram

Show how the player moves through your game. Draw boxes for each screen/state and arrows showing what happens next. Example: Start Screen → (press Space) → Gameplay → (lose all lives) → Game Over → (press R) → Start Screen

📷 Upload player flow diagram

2.5 — Design Decisions

Why did you choose this type of game? What did you change from your first idea?

Design Annotations explain WHY you made your visual choices. Development Screenshots show your Scratch code and prove you built the game yourself.

3.1 — Colour Palette & Art Style

What colours and style did you use? Why do they suit your game?

🌱 Design vocabulary (click to copy)

contrast bright colours dark colours warm colours cool colours consistent theme cartoon style pixel art atmosphere

🌱 Example answer

“I used bright, warm colours (orange, yellow, red) because my game is a fun, energetic fruit-catching game. The background is a light blue sky which creates contrast with the colourful fruit sprites. I kept the colours consistent across all backdrops to make the game feel unified.”

3.2 — Sprite & Backdrop Choices

What sprites (characters/objects) and backdrops did you use? Did you use Scratch’s built-in library, draw your own, or upload images?

3.3 — Scratch Development Screenshots

Take screenshots showing your Scratch project. Show the stage with your game running and your code blocks. To screenshot: press PrtSc (Windows) or Cmd+Shift+4 (Mac).

What to screenshot:
• Screenshot 1: Your game running on the Stage (click the green flag first, then screenshot)
• Screenshot 2: Your code blocks for the main sprite (show the Scripts area)

Screenshot 1 — Your Game Running

📷 Upload screenshot of your game running

Screenshot 2 — Your Code Blocks

📷 Upload screenshot of your code blocks

Screenshot 3 (optional) — Another Feature

📷 Upload additional screenshot (optional)

3.4 — Code Explanation

Look at your code screenshot above. Explain what your main code blocks do. You don’t need to explain every block — just describe the most important parts of your code.

🌱 Example explanation

“When the green flag is clicked, my player sprite goes to the starting position (x: 0, y: -120). Then a forever loop checks if the arrow keys are pressed. If the right arrow is pressed, the sprite moves 10 steps to the right. I also have an ‘if touching enemy’ block that broadcasts ‘game over’ when the player hits an enemy.”

3.5 — Design Annotations

Explain the design choices in your game using the design vocabulary words above.

4.1 — Evaluate your game

Rate how well your game turned out. Click a rating, then explain why.

🎨 Visual Design

Does your game look good? Do the sprites, backdrops, and colours work together?

1 — Poor 2 — Basic 3 — Good 4 — Very Good 5 — Excellent

🎮 Gameplay & Fun Factor

Is the game fun to play? Do the controls work well? Is there a challenge?

1 — Poor 2 — Basic 3 — Good 4 — Very Good 5 — Excellent

💻 Use of Scratch Features

Did you use Scratch features well? (variables, clones, broadcasts, custom blocks, sounds)

1 — Poor 2 — Basic 3 — Good 4 — Very Good 5 — Excellent

4.2 — Did My Game Match My Plan?

Look back at your sketches and Game Design Document. Is your final game the same as your plan? What changed?

4.3 — What I Would Improve

If you had more time, what would you add or change?

4.4 — Reflection

What did you learn from this project? What was hard? What are you proud of?

✅ Final Submission Checklist

Before you submit, tick off each item to make sure you haven’t missed anything!

📂 Drop or click to upload student JSON file

Section 1 — Statement of Intent & Research / 5

Section 2 — Game Design & Development / 5

Section 3 — Annotations & Dev Screenshots / 3

Section 4 — Evaluation / 2

Section 5 — Game Product: Visual Design & Feel / 5

Section 6 — Game Product: Functionality & Mechanics / 5

Overall Comments

🚀 Getting Started with Scratch

STATEMENT OF INTENT & RESEARCH

➕ Plus (what’s good)

➖ Minus (what’s bad)

❓ Interesting

GAME DESIGN & DEVELOPMENT

Screen 1: Start / Title

Screen 2: Gameplay

Screen 3: Game Over

Screen 4 (optional)

DESIGN ANNOTATIONS & DEVELOPMENT SCREENSHOTS

EVALUATION

🎨 Visual Design

🎮 Gameplay & Fun Factor

💻 Use of Scratch Features

✅ Final Submission Checklist