Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

provide-mock-data

Étoiles2

Forks1

Mis à jour24 juin 2026 à 06:02

Process for creating mock data sources in the infrastructure layer.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

anoopsg

anoopsg/agent_rules

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	provide-mock-data
description	Process for creating mock data sources in the infrastructure layer.

Provide Mock Data

When you need to create mock data for development or prototyping, follow these guidelines:

Location: Place mock data files inside the lib/src/infrastructure/_mock/ directory.
Naming: Name the file using the domain name suffixed with _mock.dart (e.g., notifications_mock.dart).
Structure:
- Provide a pure function or constants to generate the mock data.
- Do NOT use singletons or hold state within the mock data file itself. State should be managed by Riverpod providers/notifiers.
Integration: Create a repository class (e.g., NotificationsRepository) that uses the mock data generator to simulate API responses, including adding artificial delays using Future.delayed to simulate network latency.
Separation of Concerns: The notifier should handle all local state updates, while the repository strictly handles the "network" (mock) operations.

Plus depuis ce dépôt

même dépôt

create-ui-widget

anoopsg/agent_rules

Process for building, exporting, and registering reusable UI components in the packages/app_ui package. References design-to-code.md for design tokens (typography, colors, spacing).

2026-06-162

design-to-code

anoopsg/agent_rules

Outlines the process for converting Figma designs into a structured, platform-aware Flutter implementation.

2026-06-162

remove-web-platform

anoopsg/agent_rules

Use when completely removing the web platform from the project. Details how to delete directories/configurations, clean up app_ui web components, remove web-specific feature views (*_view_web.dart), prune conditional imports/logic, and run validation.

2026-06-162

manage-routes

anoopsg/agent_rules

Use when asked to add, update, or group routes using GoRouter, or manage redirection guards.

2026-06-122

flutter-golden-testing

anoopsg/agent_rules

Step-by-step workflow for creating, configuring, and updating Flutter golden tests using the Alchemist package.

2026-06-102

create-feature

anoopsg/agent_rules

Use when asked to create a new feature or sub-feature following the DDD-lite architecture, or set up state, view, and page layers for a domain.

2026-06-052

name	provide-mock-data
description	Process for creating mock data sources in the infrastructure layer.

Provide Mock Data

When you need to create mock data for development or prototyping, follow these guidelines:

Location: Place mock data files inside the lib/src/infrastructure/_mock/ directory.
Naming: Name the file using the domain name suffixed with _mock.dart (e.g., notifications_mock.dart).
Structure:
- Provide a pure function or constants to generate the mock data.
- Do NOT use singletons or hold state within the mock data file itself. State should be managed by Riverpod providers/notifiers.
Integration: Create a repository class (e.g., NotificationsRepository) that uses the mock data generator to simulate API responses, including adding artificial delays using Future.delayed to simulate network latency.
Separation of Concerns: The notifier should handle all local state updates, while the repository strictly handles the "network" (mock) operations.