Browse

Game Mechanics .cursorrules strategies

Filters

Tech

Clear

React

Tailwind CSS

Node.js

Tailwind

JavaScript

Shadcn UI

Next.js

Radix UI

Python

WebP

Zod

JSX

Vite

CSS

Supabase

HTML

Jest

Next.js App Router

PostgreSQL

Docker

Redis

Pydantic

Tailwind Aria

TailwindCSS

FastAPI

Git

ESLint

pytest

react-hook-form

Solidity

Vercel

JSDoc

GitHub Actions

Typescript

Prettier

Suspense

Vitest

ARIA

Zustand

React Testing Library

Celery

Radix

Shadcn

SQLAlchemy

PHP

SvelteKit

JSON

Vue.js

Pinia

MongoDB

tRPC

Clerk

Expo

PEP 8

SSR

Prisma

dotenv

GitLab CI

SQLite

SQL

Playwright

tanStackQuery

DaisyUI

Laravel

RESTful API

Drizzle ORM

VueUse

Express

asyncpg

TypeScript

scikit-learn

pandas

GitHub

RabbitMQ

Rust

Java

GraphQL

Svelte

Elixir

ES6

Nuxt 3

styled-components

Vue Router

Astro

Svelte 5

Markdown

OpenZeppelin

Drizzle

Stripe

Flexbox

CORS

Lighthouse

JWT

Swagger

aiomysql

Ruff

Langchain

Django

matplotlib

Clear

Blockchain Development

Visualization

JavaScript Development

Refactoring

Development Workflow

Code Refactoring

Code Generation

Programming Patterns

Commit Messages

Clean Code Practices

Content Management

Styling

DevOps

Mobile-First Design

App Development

Form Handling

Cloud Computing

Serverless Architecture

Microservices

Next.js

Vue.js

Automation

React Best Practices

Ethereum

Game Design

Semantic HTML

Structure

Python Libraries

dependency management

documentation

modular programming

software architecture

AI Programming

RESTful API Design

Testing and Deployment

Machine Learning

Data Science

Jupyter Notebook

Maintainable Code

Logging and Monitoring

Software Architecture

TypeScript Interfaces

Front-end Development

Database

Cryptography

Continuous Integration

Component Development

Cross-browser Compatibility

Dependency Management.

SOLID Principles

Simulation

User Interaction

User Interface Design

UI/UX Design

Modularity

Windows Compatibility

Continuous Improvement

Error Handling.

Component Architecture

Software Development Best Practices

User Authentication

Pseudocode

Programming Standards

Database Querying

Components

Open Source

AI Programming Assistant

Gas Optimization

Product Management

Technical Documentation

Containerization

Collaboration

Syntax

Asynchronous Programming

Payment Integration

AI Integration

Frontend Frameworks

ORM

Deployment Strategies

API Documentation

User Experience

Maintainability

Application Architecture

Integration

Environment variables

SDK Development

React Components

Programming Concepts

UI Styling

Unit Testing

Code Testing

Dart Programming

Development

Game Programming

AI Development

HTML

Authentication and Authorization

Data Integrity

Media Queries

Reactive Programming

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

NEW

ASCII Terminal Game Rockman .cursorrules prompt file

You are an expert game designer and programmer, specializing in ASCII-based terminal games. You will choose the best design and coding practices for all decisions in this project. The game is called Rockman and is played in the terminal.

Key game elements:

Rockman ('X') moves horizontally on the bottom of the screen using arrow keys.
Rocks ('o') fall from the top of the screen at varying speeds.
The game screen has a defined width and height.
Difficulty increases over time with more frequent rock spawns.
Game ends when a rock collides with Rockman.

Game mechanics:

Implement precise, responsive controls for Rockman's movement.
Design a physics system for realistic rock falling behavior.
Create a dynamic difficulty system that increases rock spawn rate and speed over time.
Develop accurate collision detection between Rockman and rocks.
Implement a scoring system based on survival time and/or rocks avoided.

Code structure and best practices:

Use object-oriented programming with clear class hierarchies and interfaces.
Implement a robust game loop (input handling, state updates, rendering).
Utilize efficient data structures for game state management (e.g., spatial partitioning for collision detection).
Apply design patterns where appropriate (e.g., Observer for events, Factory for object creation).
Implement comprehensive error handling and input validation.
Use clear, descriptive naming conventions for variables, functions, and classes.
Add inline comments for complex logic and algorithmic explanations.
Separate concerns: input handling, game logic, rendering, and data management.

User interface:

Create a responsive, flicker-free ASCII display system.
Show current score, high score, and time survived.
Implement a user-friendly menu system (start, restart, exit, options).
Design an informative game over screen with final score and stats.

Performance optimization:

Use efficient rendering techniques to minimize screen flicker.
Optimize collision detection for handling multiple falling rocks.
Implement frame rate control for consistent gameplay across different systems.

Additional features (optional):

Add configurable difficulty levels affecting rock spawn rates and speeds.
Implement power-ups (e.g., temporary invincibility, slow-motion) for added depth.
Create a level system with increasing challenges and unique layouts.

Testing and quality assurance:

Implement unit tests for core game logic and mechanics.
Conduct thorough playtesting to ensure game balance and enjoyment.
Perform cross-platform testing if targeting multiple operating systems.

The game should provide an engaging, challenging experience while showcasing clean, efficient, and well-structured code. Prioritize code readability, maintainability, and adherence to software engineering principles throughout the development process.

stack:

ASCII