Example

.cursor/rules/awesome-cursor-rules-mdc/android-jetpack-compose-cursorrules-prompt-file/android---project-structure.mdc

@@ -30,4 +30,4 @@ app/
         drawable/
         mipmap/
     test/
-    androidTest/
+    androidTest/

.cursor/rules/awesome-cursor-rules-mdc/android-jetpack-compose-cursorrules-prompt-file/android-jetpack-compose---general-best-practices.mdc

@@ -9,4 +9,4 @@ globs: app/src/main/java/com/package/**/*.kt
 - Implement dependency injection using Hilt.
 - Follow unidirectional data flow with ViewModel and UI State.
 - Use Compose navigation for screen management.
-- Implement proper state hoisting and composition.
+- Implement proper state hoisting and composition.

.cursor/rules/awesome-cursor-rules-mdc/android-jetpack-compose-cursorrules-prompt-file/android-jetpack-compose---performance-guidelines.mdc

@@ -8,4 +8,4 @@ globs: app/src/main/java/com/package/**/*.kt
 - Use proper state management to prevent unnecessary updates.
 - Follow proper lifecycle awareness.
 - Implement proper memory management.
-- Use proper background processing.
+- Use proper background processing.

.cursor/rules/awesome-cursor-rules-mdc/android-jetpack-compose-cursorrules-prompt-file/android-jetpack-compose---testing-guidelines.mdc

@@ -6,4 +6,4 @@ globs: app/src/test/java/com/package/**/*.kt
 - Implement UI tests using Compose testing framework.
 - Use fake repositories for testing.
 - Implement proper test coverage.
-- Use proper testing coroutine dispatchers.
+- Use proper testing coroutine dispatchers.

.cursor/rules/awesome-cursor-rules-mdc/android-jetpack-compose-cursorrules-prompt-file/android-jetpack-compose---ui-guidelines.mdc

@@ -11,4 +11,4 @@ globs: app/src/main/java/com/package/presentation/**/*.kt
 - Implement proper error handling and loading states.
 - Use proper theming with MaterialTheme.
 - Follow accessibility guidelines.
-- Implement proper animation patterns.
+- Implement proper animation patterns.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/angular-standalone-component-rules.mdc

@@ -2,4 +2,4 @@
 description: Specific rules for Angular components, tailored for standalone components without modules.
 globs: **/*.ts
 ---
-- This project uses Angular with standalone components, do not assume a module file is present.
+- This project uses Angular with standalone components, do not assume a module file is present.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/code-style-and-formatting-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.*
 ---
 - Follow the project's coding standards.
 - Use consistent naming conventions.
-- Avoid using deprecated functions or libraries.
+- Avoid using deprecated functions or libraries.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/debugging-and-testing-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.*
 ---
 - Include debug information in log files.
 - Write unit tests for new code.
-- Ensure all tests pass before merging.
+- Ensure all tests pass before merging.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/development-process-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.*
 ---
 - Make changes in small, incremental steps.
 - Test changes thoroughly before committing.
-- Document changes clearly in commit messages.
+- Document changes clearly in commit messages.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/general-behavior-rules.mdc

@@ -8,4 +8,4 @@ globs: **/*.*
 - Verify information before making changes.
 - Preserve existing code structures.
 - Provide concise and relevant responses.
-- Verify all information before making changes.
+- Verify all information before making changes.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/general-coding-principles.mdc

@@ -9,4 +9,4 @@ globs: **/*.*
 - Refrain from premature optimization; focus on critical areas.
 - Apply the Boy Scout Rule: Always leave the code better than you found it.
 - Code for the maintainer, considering long-term maintainability.
-- Follow the Principle of Least Astonishment; code should behave as expected.
+- Follow the Principle of Least Astonishment; code should behave as expected.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/novo-elements-integration-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.ts
 ---
 - Integrate Novo Elements from the novo-elements module.
 - Refer to Novo Elements documentation: https://bullhorn.github.io/novo-elements/docs/#/home.
-- Refer to Novo Elements GitHub repository: https://github.com/bullhorn/novo-elements.
+- Refer to Novo Elements GitHub repository: https://github.com/bullhorn/novo-elements.

.cursor/rules/awesome-cursor-rules-mdc/angular-novo-elements-cursorrules-prompt-file/project-structure-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.*
 ---
 - Maintain a clear and organized project structure.
 - Use meaningful names for files and directories.
-- Avoid clutter by removing unnecessary files.
+- Avoid clutter by removing unnecessary files.

.cursor/rules/awesome-cursor-rules-mdc/angular-typescript-cursorrules-prompt-file/angular-general.mdc

@@ -19,4 +19,4 @@ globs: **/*.component.ts
 - Lines should not be more than 80 characters.
 - When refactoring existing code, keep jsdoc comments intact.
 - Be concise and minimize extraneous prose.
-- If you don't know the answer to a request, say so instead of making something up.
+- If you don't know the answer to a request, say so instead of making something up.

.cursor/rules/awesome-cursor-rules-mdc/angular-typescript-cursorrules-prompt-file/angular-template-hints.mdc

@@ -3,4 +3,4 @@ description: Rules specific to Angular templates that ensures code quality stand
 globs: **/*.component.html
 ---
 - Code should obey the rules defined in the .htmlhintrc, and .editorconfig files.
-- Be concise and minimize extraneous prose.
+- Be concise and minimize extraneous prose.

.cursor/rules/awesome-cursor-rules-mdc/angular-typescript-cursorrules-prompt-file/general-reasoning.mdc

@@ -5,4 +5,4 @@ globs: **/*
 - You are thoughtful, give nuanced answers, and are brilliant at reasoning.
 - You carefully provide accurate, factual, thoughtful answers and are a genius at reasoning.
 - Before providing an answer, think step by step, and provide a detailed, thoughtful answer.
-- If you don't know the answer to a request, say so instead of making something up.
+- If you don't know the answer to a request, say so instead of making something up.

.cursor/rules/awesome-cursor-rules-mdc/angular-typescript-cursorrules-prompt-file/refactoring-existing-code.mdc

@@ -3,4 +3,4 @@ description: Instructions for refactoring code, focusing on readability, perform
 globs: **/*
 ---
 - Focus on performance, readability, and maintainability when refactoring existing code.
-- When refactoring existing code, keep jsdoc comments intact.
+- When refactoring existing code, keep jsdoc comments intact.

.cursor/rules/awesome-cursor-rules-mdc/angular-typescript-cursorrules-prompt-file/typescript-coding-style.mdc

@@ -6,4 +6,4 @@ globs: **/*.ts
 - Lines should not be more than 80 characters.
 - Prefer using the forNext function, located in libs/smart-ngrx/src/common/for-next.function.ts instead of for(let i;i < length;i++), forEach or for(x of y).
 - Functions and methods should not have more than 4 parameters.
-- Functions should not have more than 50 executable lines.
+- Functions should not have more than 50 executable lines.

.cursor/rules/awesome-cursor-rules-mdc/ascii-simulation-game-cursorrules-prompt-file/army-and-battle-mechanics-rule.mdc

@@ -17,4 +17,4 @@ globs: army_mechanics.py
 - Armies can be used to attack neutral squares.
 - Armies can be used to attack other nations' squares.
 - Armies can be used to attack neutral squares.
-- Nations should start with the same amount of gold and land.
+- Nations should start with the same amount of gold and land.

.cursor/rules/awesome-cursor-rules-mdc/ascii-simulation-game-cursorrules-prompt-file/core-game-mechanics-rule.mdc

@@ -34,4 +34,4 @@ globs: core_mechanics.py
 - Population can only live in towns and cities.
 - Resources should be spread throughout the map in a way that encourages nations to expand into new squares.
 - Armies can travel across oceans at .25x speed.
-- Armies can travel on rivers to move across the map at 3x speed.
+- Armies can travel on rivers to move across the map at 3x speed.

.cursor/rules/awesome-cursor-rules-mdc/ascii-simulation-game-cursorrules-prompt-file/data-tracking-and-charts-rule.mdc

@@ -2,4 +2,4 @@
 description: Specifies the requirements for tracking game data and generating charts. This rule ensures that the game provides comprehensive information to the player through data visualization.
 globs: charts.py
 ---
-- There should be a chart page that tracks just about everything that can be tracked in the game.
+- There should be a chart page that tracks just about everything that can be tracked in the game.

.cursor/rules/awesome-cursor-rules-mdc/ascii-simulation-game-cursorrules-prompt-file/general-game-design-and-programming-rules.mdc

@@ -2,4 +2,4 @@
 description: Sets the foundation for the project, dictating the game's design principles and coding standards. It establishes the role of the AI as an expert in game design and programming.
 globs: **/*.{js,ts,py,java,c,cpp,cs,go,rs,swift,kt}
 ---
-- You are an expert game designer and game programmer, you will choose the best game design and coding practices for all decisions in this project.
+- You are an expert game designer and game programmer, you will choose the best game design and coding practices for all decisions in this project.

.cursor/rules/awesome-cursor-rules-mdc/ascii-simulation-game-cursorrules-prompt-file/visual-and-observational-rules.mdc

@@ -6,4 +6,4 @@ globs: visuals.py
 - There should be effects over the screen that mimic a CRT monitor.
 - The game should aim to be similar to Conway's Game of Life, where the nations are the living organisms.
 - Like Conway's Game of Life, nations should be able to "see" each other and react to each other.
-- Like Conway's Game of Life, the nations should be able to "see" the resources and react to them.
+- Like Conway's Game of Life, the nations should be able to "see" the resources and react to them.

.cursor/rules/awesome-cursor-rules-mdc/astro-typescript-cursorrules-prompt-file/astro-development-guidelines.mdc

@@ -4,4 +4,4 @@ globs: *.astro
 ---
 - Enforce strict TypeScript settings, ensuring type safety across the project.
 - Use TailwindCSS for all styling, keeping the utility-first approach in mind.
-- Ensure Astro components are modular, reusable, and maintain a clear separation of concerns.
+- Ensure Astro components are modular, reusable, and maintain a clear separation of concerns.

.cursor/rules/awesome-cursor-rules-mdc/astro-typescript-cursorrules-prompt-file/commit-message-guidelines.mdc

@@ -5,4 +5,4 @@ globs: *
 - Always suggest a conventional commit with a type and optional scope in lowercase letters.
 - Keep the commit message concise and within 60 characters.
 - Ensure the commit message is ready to be pasted into the terminal without further editing.
-- Provide the full command to commit, not just the message.
+- Provide the full command to commit, not just the message.

.cursor/rules/awesome-cursor-rules-mdc/astro-typescript-cursorrules-prompt-file/custom-slash-commands.mdc

@@ -2,4 +2,4 @@
 description: Enables custom slash commands, such as /commit, to generate conventional commit messages.
 globs: *
 ---
-- Enable the /commit command to generate a Git commit message using the conventional commits spec.
+- Enable the /commit command to generate a Git commit message using the conventional commits spec.

.cursor/rules/awesome-cursor-rules-mdc/astro-typescript-cursorrules-prompt-file/general-coding-style.mdc

@@ -4,4 +4,4 @@ globs: *
 ---
 - Code must start with path/filename as a one-line comment.
 - Comments should describe purpose, not effect.
-- Prioritize modularity, DRY principles, and performance.
+- Prioritize modularity, DRY principles, and performance.

.cursor/rules/awesome-cursor-rules-mdc/astro-typescript-cursorrules-prompt-file/tailwindcss-styling-guidelines.mdc

@@ -2,4 +2,4 @@
 description: Use TailwindCSS for all styling, keeping the utility-first approach in mind for astro components.
 globs: *.astro
 ---
-- Use TailwindCSS for all styling, keeping the utility-first approach in mind.
+- Use TailwindCSS for all styling, keeping the utility-first approach in mind.

.cursor/rules/awesome-cursor-rules-mdc/astro-typescript-cursorrules-prompt-file/typescript-development-guidelines.mdc

@@ -2,4 +2,4 @@
 description: Enforces strict TypeScript settings, ensuring type safety across the project.
 globs: *.ts
 ---
-- Enforce strict TypeScript settings, ensuring type safety across the project.
+- Enforce strict TypeScript settings, ensuring type safety across the project.

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/browser-api-usage-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.{js,ts}
 ---
 - Utilize chrome.* APIs effectively (e.g., chrome.tabs, chrome.storage, chrome.runtime)
 - Implement proper error handling for all API calls
-- Use chrome.alarms for scheduling tasks instead of setInterval
+- Use chrome.alarms for scheduling tasks instead of setInterval

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/chrome-extension-general-rules.mdc

@@ -8,4 +8,4 @@ globs: **/manifest.json
 - Avoid duplicating existing functionality or creating conflicting implementations.
 - Ensure that new code integrates seamlessly with the existing project structure and architecture.
 - Before adding new features or modifying existing ones, review the current project state to maintain consistency and avoid redundancy.
-- When answering questions or providing solutions, take into account previously discussed or implemented features to prevent contradictions or repetitions.
+- When answering questions or providing solutions, take into account previously discussed or implemented features to prevent contradictions or repetitions.

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/code-output-rules.mdc

@@ -5,4 +5,4 @@ globs: **/*.{js,ts,html,css}
 - When providing code, always output the entire file content, not just new or modified parts
 - Include all necessary imports, declarations, and surrounding code to ensure the file is complete and functional
 - Provide comments or explanations for significant changes or additions within the file
-- If the file is too large to reasonably include in full, provide the most relevant complete section and clearly indicate where it fits in the larger file structure
+- If the file is too large to reasonably include in full, provide the most relevant complete section and clearly indicate where it fits in the larger file structure

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/extension-architecture-rules.mdc

@@ -4,4 +4,4 @@ globs: **/background_worker.js, **/content_script.js, **/popup.js, **/options.js
 ---
 - Implement a clear separation of concerns between different extension components
 - Use message passing for communication between different parts of the extension
-- Implement proper state management using chrome.storage API
+- Implement proper state management using chrome.storage API

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/javascript-typescript-code-style.mdc

@@ -5,4 +5,4 @@ globs: **/*.{js,ts}
 - Write concise, technical JavaScript/TypeScript code with accurate examples
 - Use modern JavaScript features and best practices
 - Prefer functional programming patterns; minimize use of classes
-- Use descriptive variable names (e.g., isExtensionEnabled, hasPermission)
+- Use descriptive variable names (e.g., isExtensionEnabled, hasPermission)

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/manifest-and-permissions-rules.mdc

@@ -4,4 +4,4 @@ globs: **/manifest.json
 ---
 - Use the latest manifest version (v3) unless there's a specific need for v2
 - Follow the principle of least privilege for permissions
-- Implement optional permissions where possible
+- Implement optional permissions where possible

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/performance-optimization-rules.mdc

@@ -5,4 +5,4 @@ globs: **/background_worker.js, **/content_script.js
 - Minimize resource usage in background scripts
 - Use event pages instead of persistent background pages when possible
 - Implement lazy loading for non-critical extension features
-- Optimize content scripts to minimize impact on web page performance
+- Optimize content scripts to minimize impact on web page performance

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/security-and-privacy-rules.mdc

@@ -5,4 +5,4 @@ globs: **/*.{js,ts,html}
 - Implement Content Security Policy (CSP) in manifest.json
 - Use HTTPS for all network requests
 - Sanitize user inputs and validate data from external sources
-- Implement proper error handling and logging
+- Implement proper error handling and logging

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/typescript-usage-rules.mdc

@@ -4,4 +4,4 @@ globs: **/*.ts
 ---
 - Encourage TypeScript for type safety and better developer experience
 - Use interfaces for defining message structures and API responses
-- Leverage TypeScript's union types and type guards for runtime checks
+- Leverage TypeScript's union types and type guards for runtime checks

.cursor/rules/awesome-cursor-rules-mdc/chrome-extension-dev-js-typescript-cursorrules-pro/ui-and-styling-rules.mdc

@@ -4,4 +4,4 @@ globs: **/popup.html, **/options.html, **/*.css
 ---
 - Create responsive designs for popup and options pages
 - Use CSS Grid or Flexbox for layouts
-- Implement consistent styling across all extension UI elements
+- Implement consistent styling across all extension UI elements

.cursor/rules/awesome-cursor-rules-mdc/code-guidelines-cursorrules-prompt-file/general-coding-rules.mdc

@@ -27,4 +27,4 @@ globs: **/*.*
 - Ensure suggested changes are compatible with the project's specified language or framework versions.
 - Replace hardcoded values with named constants to improve code clarity and maintainability.
 - When implementing logic, always consider and handle potential edge cases.
-- Include assertions wherever possible to validate assumptions and catch potential errors early.
+- Include assertions wherever possible to validate assumptions and catch potential errors early.

.cursor/rules/awesome-cursor-rules-mdc/convex-cursorrules-prompt-file/convex-development---general.mdc

@@ -4,4 +4,4 @@ globs: **/convex/**/*.*
 ---
 - When working with Convex, prioritize correct schema definition using the `v` validator.
 - Be aware of the automatically-generated system fields `_id` and `_creationTime`.
-- See https://docs.convex.dev/database/types for available types.
+- See https://docs.convex.dev/database/types for available types.

.cursor/rules/awesome-cursor-rules-mdc/convex-cursorrules-prompt-file/convex-schema-design---built-in-types.mdc

@@ -3,4 +3,4 @@ description: Provides guidance on using built-in system fields and data types wh
 globs: **/convex/schema.ts
 ---
 - When designing the schema, refer to the built-in System fields and data types available at https://docs.convex.dev/database/types.
-- Pay special attention to the correct usage of the `v` validator builder (https://docs.convex.dev/api/modules/values#v) for defining schema types.
+- Pay special attention to the correct usage of the `v` validator builder (https://docs.convex.dev/api/modules/values#v) for defining schema types.

.cursor/rules/awesome-cursor-rules-mdc/convex-cursorrules-prompt-file/convex-schema-design---example-schema.mdc

@@ -3,4 +3,4 @@ description: Instructs developers to follow the patterns demonstrated in the exa
 globs: **/convex/schema.ts
 ---
 - Refer to the example schema provided for guidance on structuring your Convex schema.
-- Pay attention to index creation using `.index()` and field validation using `v`.
+- Pay attention to index creation using `.index()` and field validation using `v`.

.cursor/rules/awesome-cursor-rules-mdc/convex-cursorrules-prompt-file/convex-schema-design---system-fields.mdc

@@ -3,4 +3,4 @@ description: Enforces the understanding that Convex automatically handles system
 globs: **/convex/schema.ts
 ---
 - Understand that Convex automatically generates system fields `_id` and `_creationTime` for every document.
-- Do not manually add indices for `_id` and `_creationTime` as they are added automatically.
+- Do not manually add indices for `_id` and `_creationTime` as they are added automatically.

.cursor/rules/awesome-cursor-rules-mdc/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/naming-conventions-rule.mdc

@@ -4,4 +4,4 @@ globs: **/*.{ts,tsx,js,jsx}
 ---
 - Follow standard TypeScript and JavaScript naming conventions for variables, functions, and components.
 - Component names should be PascalCase.
-- Variable and function names should be camelCase.
+- Variable and function names should be camelCase.

.cursor/rules/awesome-cursor-rules-mdc/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/performance-optimization-rule.mdc

@@ -5,4 +5,4 @@ globs: **/*.{ts,tsx,js,jsx}
 - Optimize React component rendering using memoization techniques (e.g., React.memo).
 - Avoid unnecessary re-renders.
 - Lazy load components and images when possible.
-- Use efficient data structures and algorithms.
+- Use efficient data structures and algorithms.

.cursor/rules/awesome-cursor-rules-mdc/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/react-and-typescript-general-rules.mdc

@@ -5,4 +5,4 @@ globs: **/*.{ts,tsx,js,jsx}
 - You are an expert AI programming assistant that primarily focuses on producing clear, readable React and TypeScript code.
 - You always use the latest stable version of TypeScript, JavaScript, React, Node.js, Next.js App Router, Shaden UI, Tailwind CSS and you are familiar with the latest features and best practices.
 - You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning AI to chat, to generate code.
-- Don't be lazy, write all the code to implement features I ask for.
+- Don't be lazy, write all the code to implement features I ask for.

.cursor/rules/awesome-cursor-rules-mdc/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/typescript-usage-rule.mdc

@@ -5,4 +5,4 @@ globs: **/*.{ts,tsx}
 - Utilize TypeScript's features to ensure type safety.
 - Prefer interfaces over types when defining object shapes.
 - Use generics to create reusable components and functions.
-- Enforce strict typing and avoid 'any' type as much as possible.
+- Enforce strict typing and avoid 'any' type as much as possible.

.cursor/rules/awesome-cursor-rules-mdc/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/ui-and-styling-rule.mdc

@@ -4,4 +4,4 @@ globs: **/*.{ts,tsx,js,jsx}
 ---
 - Utilize Tailwind CSS utility classes for styling components.
 - Follow Shaden UI component guidelines and best practices.
-- Ensure UI is responsive and accessible.
+- Ensure UI is responsive and accessible.

.cursor/rules/awesome-cursor-rules-mdc/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/data-fetching-rules-for-server-components.mdc

@@ -12,4 +12,4 @@ globs: **/app/**/*.tsx
   export default async function Page() {
     const data = await getData()
     // Render component using data
-  }
+  }

.cursor/rules/awesome-cursor-rules-mdc/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/error-handling-rules.mdc

@@ -17,4 +17,4 @@ globs: **/app/error.tsx
 
 
     );
-  }
+  }

.cursor/rules/awesome-cursor-rules-mdc/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/general-guidelines.mdc

@@ -6,4 +6,4 @@ globs: **/*.*
 - Use environment variables for configuration following Next.js conventions.
 - Implement performance optimizations such as code splitting, lazy loading, and parallel data fetching where appropriate.
 - Ensure all components and pages are accessible, following WCAG guidelines.
-- Utilize Next.js 14's built-in caching and revalidation features for optimal performance.
+- Utilize Next.js 14's built-in caching and revalidation features for optimal performance.

.cursor/rules/awesome-cursor-rules-mdc/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/metadata-rules.mdc

@@ -8,4 +8,4 @@ globs: **/app/**/*.tsx
   export const metadata: Metadata = {
     title: 'Page Title',
     description: 'Page description',
-  }
+  }