Project Rules and Guidelines
Indexes a documentation directory with links to architecture, workflow, testing, and security guides for a Figma-based resume project.
What this file does
Indexes a documentation directory with links to architecture, workflow, testing, and security guides for a Figma-based resume project.
When to use it
- Onboarding new contributors to a project with multiple documentation files
- Setting up a central README for a docs folder in a frontend repository
- Providing a quick reference to project conventions and domain concepts
- Establishing a documentation entry point for a Figma-integrated application
Assumes this stack
source: .cursorrules type: cursorrules
Project Rules and Guidelines
Auto-generated from .context/docs on 2026-02-23T20:51:48.350Z
README
Documentation Overview
Welcome to the documentation directory of the Resume Figma project. This README serves as an entry point and index to the comprehensive guides and resources available within the docs/ folder to help developers, contributors, and stakeholders understand and effectively work with the repository.
Contents of the docs/ Directory
The docs/ folder contains in-depth markdown files covering all major aspects of the project, including architecture, development workflows, testing, domain concepts, and more. These guides are designed to provide clarity on the repository layout, coding conventions, and operational practices.
Core Guides
-
Project Overview
Introduction to the project’s purpose, goals, and high-level roadmap. It outlines the key features and stakeholders involved. -
Architecture Notes
Details the structural design, component organization, technology stack, and architectural rationale. Includes diagrams and explanations of major modules and their responsibilities. -
Development Workflow
Explains the branching strategy, commit conventions, CI/CD processes, and coding standards to streamline contributions and maintain code quality. -
Testing Strategy
Describes testing frameworks, coverage targets, types of tests (unit, integration, end-to-end), and guidelines for writing effective tests. -
Glossary & Domain Concepts
Defines key business terms, user personas, domain models, and concepts relevant to the application domain. -
Data Flow & Integrations
Illustrates data pipelines, external integrations, APIs, and event-driven interactions that the system relies on or exposes. -
Security & Compliance Notes
Covers authentication and authorization models, data privacy controls, secrets management, and compliance with relevant standards. -
Tooling & Productivity Guide
Provides information on development tools, IDE configurations, scripts, and automation to boost developer productivity.
Repository Snapshot
The project repository contains the following top-level files and directories:
- Source and UI components (e.g.,
components/,resume/components/) - Entry points and configuration files (
main.tsx,package.json,vite.config.ts) - TypeScript configurations (
tsconfig.json, etc.) - Additional documentation and changelogs (
CHANGELOG.md,README.md) - Scripts and styles folders for auxiliary resources
How to Use This Documentation
- Start by reading the Project Overview to gain a broad understanding of the repository’s intent and scope.
- Consult the Architecture Notes for insight into the design and key patterns, especially if you plan to extend or refactor the codebase.
- Follow the Development Workflow guide for contribution guidelines and to understand the CI/CD pipeline.
- Leverage the Testing Strategy when writing or maintaining tests to ensure quality and reliability.
- Reference the Glossary to familiarize yourself with domain-specific terminology.
- Review the Data Flow & Integrations and Security & Compliance guides for operational and security-related considerations.
- Use the Tooling & Productivity Guide to streamline your local setup and development tasks.
Cross-References
- Many UI components follow consistent conventions documented in the architecture and can be found under
components/uiandresume/components/ui. - Utility functions, hooks (e.g.,
useIsMobile), and shared types likeChartConfigare defined in these UI directories and adhere to patterns described in the architectural guides. - The modular component design supports flexible resume-building features, integrated with Figma-based UI elements located in
components/figmaandresume/components/figma.
For any further questions or contributions, please refer to the contribution guidelines in the development-workflow.md and consult your team lead or project maintainer.
Happy coding!
What's inside
8 linked guide sections, a repository snapshot, and usage instructions
Change this for your project
- Replace
plgs2005/resume_figmawith your own repository name - Replace
Resume Figma projectwith your project's name - Replace the auto-generated timestamp
2026-02-23T20:51:48.350Zwith your own
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Auto-generating a timestamp to keep documentation freshness visible
- Linking to separate markdown files for each major concern (architecture, testing, security)
Related Documents
dbt Core
Defines a complete dbt project setup with layered architecture, SQL style, Jinja best practices, and CI/CD workflow guidance.
HarmonyOS 主题与样式 - Cursor Rules
Defines HarmonyOS theming rules for dark/light mode, page brightness, and screen-on control with code examples.
Cursor Development Environment
Documents a Docker-based dev container setup with test commands and OpenClaw agent configuration for the ClawDrive project.
Journey from Concept to Code: Transforming Cursor into a Devin-like AI Assistant
Documents the creation of aicode.cursorrules, a set of rules that turns Cursor/Windsurf into a Devin-like AI assistant with automated planning and self-evolution.