DynamoDS/DynamoHome

Dernière activité source enregistrée: 27 avril 2026 à 14:51

Catalogue SkillsMP mis à jour: 5 novembre 2026 à 19:57

skills collectés: 1

Étoiles GitHub: 3
Forks GitHub: 8

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/DynamoDS/DynamoHome.

README du dépôt

Fichier source du README : README.md

Lire le README source

Afficher le README complet

# DynamoHome [![License](https://img.shields.io/npm/l/@dynamods/dynamo-home)](https://github.com/DynamoDS/DynamoHome/blob/master/LICENSE) [![version](https://img.shields.io/npm/v/@dynamods/dynamo-home?logo=npm&label=version)](https://www.npmjs.com/package/@dynamods/dynamo-home) [![Build](https://github.com/DynamoDS/DynamoHome/actions/workflows/build.yml/badge.svg)](https://github.com/DynamoDS/DynamoHome/actions/workflows/build.yml) [![Publish](https://github.com/DynamoDS/DynamoHome/actions/workflows/npm-publish.yml/badge.svg)](https://github.com/DynamoDS/DynamoHome/actions/workflows/npm-publish.yml) A react-based app to serve as Dynamo landing page. This application is specific to Dynamo and utilizes several specific endpoints to work as intended. ## Introduction ### Layout The sidebar contains links to the 3 main modules: - `Recent` - lists of recently opened files (the number of recent files can be changed by the user in Dynamo preferences window) - `Samples` - lists Sample files. e.g "%ProgramData%\Autodesk\RVT 2025\Samples" - `Learning` - a one-stop-shop for Dynamo learning resources #### Recent module ![recent](https://github.com/dnenov/DynamoHomePage/assets/5354594/d47687b6-dd91-46eb-a9a3-f97eb44a7ddb) #### Samples module ![samples](https://github.com/dnenov/DynamoHomePage/assets/5354594/21279b42-3a55-4f22-8872-e084035598ba) #### Learning module ![learning](https://github.com/dnenov/DynamoHomePage/assets/5354594/c4cc53c7-8d3d-4d16-bd82-19530169c313) ## Development ### Requirements - [git](https://git-scm.com/) - [Node.js](https://nodejs.org/) ### Install ```shell git clone https://github.com/DynamoDS/DynamoHome.git cd DynamoHome npm install --legacy-peer-deps ``` ### Running the project ```shell npm start ``` ### Build for development ```shell npm run build ``` ### Create a distribution bundle ```shell npm run bundle ``` ### Lint We use [ESlint](https://eslint.org/) to analyze and find problems. It has [integrations](https://eslint.org/docs/latest/user-guide/integrations) for various editors and other tools. ```shell npm run lint:check # To find problems npm run lint:fix # To fix problems ``` ### Test We use [jest](https://jestjs.io/) and [playwright](https://playwright.dev/) to run our tests. ```shell npm run test:unit # To run unit test npm run test:e2e # To run e2e test npm run test # To runs all tests ``` ### Bump Version ```shell npm run version:patch # To bump patch version ``` ### Localization Localization is done via [`react-intl`](https://www.npmjs.com/package/react-intl) library. The current setup relies on the combination of these 2 elements: - localization files stored inside the [`src/locales`](src/locales) folder (add as many localization files as needed) - adding new locales to the switch statement inside the [`src/localization/localization.js`](src/localization/localization.js) file: ```javascript export const getMessagesForLocale = (locale) => { switch(locale) { case 'en': return EnglishMessages; default: return EnglishMessages; } } ``` ### 3rd party libraries and dependencies The use of 3rd party libraries was kept to the bare minimum, where developing native elements would have resulted in exceptional time overhead. - [`react-intl`](https://www.npmjs.com/package/react-intl) - library used for localization - [`react-split-pane`](https://www.npmjs.com/package/react-split-pane) - allows resizable (draggable) panel (used in the SidePanel) - [`react-table`](https://www.npmjs.com/package/react-table) - a lightweight headless react table ### Generate Third Party License Info - To generate about box html files use `npm run license`, this will output alternative about box files to [license_output](license_output). One will contain the full transitive production dep list, the other will contain the direct production deps. - These files will be packed into the released npm package ## Claude Code Integration This repository includes configuration files for **Claude Code** to assist with development, testing, and maintenance. The `.claude/` directory defines: - AI agents with specific roles (frontend, testing, build) - Project-specific knowledge and conventions - Reusable workflows for common tasks ### How to use Claude Code 1. Install and authenticate Claude Code (see Anthropic documentation) 2. Open a terminal at the root of this repository 3. Run: ```bash claude ``` ### Code Review and Pull Request Checks A dedicated Claude agent is available for code reviews and pull request checks. The `code-review-agent` is designed to: - Review changes for quality and consistency - Validate alignment with DynamoHome conventions - Detect potential regressions or risks - Provide actionable PR feedback #### Example prompts - “Use the code-review-agent to review this pull request” - “Review these changes as a PR and list any issues” - “Run a PR check using the code-review workflow” This helps ensure consistent, high-quality contributions while keeping reviews focused, incremental, and aligned with project standards. ### Testing Strategy with Claude Code This repository follows a strict testing responsibility model when using Claude Code. #### Test folder structure ``` tests/ unit/ # Jest unit tests App.test.tsx ComponentName.test.tsx e2e/ # Playwright end-to-end tests navigation.spec.ts # Navigation tests sidebar.spec.ts # Sidebar dropdown tests recent.spec.ts # Recent page tests samples.spec.ts # Samples page tests learning.spec.ts # Learning page and carousel tests pages/ # Page Object Model — page classes components/ # Page Object Model — component classes jest.setup.ts # Jest global setup (chrome mock) __mocks__/ # Auto-applied mocks (CSS, images, chrome WebView) ``` #### Unit Testing - Unit tests live in `tests/unit/` and are run with `npm run test:unit` - Every component and module must have unit tests - The target is 100% unit test coverage - Missing unit tests must be created when coverage gaps are found #### End-to-End Testing (Playwright) - E2E tests live in `tests/e2e/` and are run with `npm run test:e2e` - All Playwright tests must follow the Page Object Model (POM) - Pages and components must be implemented as separate classes in `tests/e2e/pages/` and `tests/e2e/components/` - Each `*.spec.ts` file must only contain test orchestration — no selectors or direct page actions #### Exploratory Testing - For exploratory testing or issue investigation, use `playwright-cli open http://localhost:8080` - Findings from exploratory testing should be converted into formal Page Object classes - Any feature without test coverage must have new tests added This setup ensures consistent test quality, clear ownership, and long-term maintainability.

Chargement du README du dépôt…

Skills dans ce dépôt

Analystes en assurance qualité des logiciels et testeurs

1 catégories métier · 100% classifié

skill

métier

description

mis à jour

playwright-cli

Analystes en assurance qualité des logiciels et testeurs

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Langue du texte source : anglais

2026-04-27

Affichage de 1 skills collectés sur 1.