Skip to main content
Run any Skill in Manus
with one click
Neha
GitHub creator profile

Neha

Repository-level view of 12 collected skills across 2 GitHub repositories.

skills collected
12
repositories
2
updated
2026-07-05
repository explorer

Repositories and representative skills

accessibility
web-and-digital-interface-designers

Review React Native code for screen-reader support, labels and roles, touch targets, focus order, colour contrast, and dynamic type. Use when building UI, reviewing components, or auditing a screen for accessibility.

2026-06-29
architecture
software-developers

Review and structure React Native features for correct folder layout, navigation, deep linking, error boundaries, rendering safety, and code quality. Use when designing a new feature, reviewing structure, or isolating crashes.

2026-06-29
code-review
software-quality-assurance-analysts-and-testers

Audit entry point for reviewing React Native code. Routes each concern to a focused skill and defines the review output format. Use when reviewing a PR, auditing a screen, or running a pre-merge quality gate.

2026-06-29
conventions
software-developers

Baseline React Native project conventions for structure, TypeScript, naming, file size, and hygiene. Use when setting up a project, writing new code, or reviewing for consistency.

2026-06-29
critical-rules
software-developers

Non-negotiable React Native rules that prevent crashes, data loss, security breaches, and compliance violations. Use on every change as a baseline safety check, regardless of the task.

2026-06-29
performance
software-developers

Review React Native code for rendering performance, list virtualisation, memoisation, image handling, animations, and memory/resource cleanup. Use when a screen feels janky, before merging UI-heavy code, or when profiling.

2026-06-29
security
software-developers

Review React Native code for secret handling, secure storage, transport security, PII in logs, deep-link validation, input validation, and privacy compliance. Use when handling auth, payments, personal data, or before a security review.

2026-06-29
spec-authoring
software-developers

Write a spec before building โ€” capturing requirements, design, and tasks in order, with traceability between them. Use when starting any non-trivial feature so work is planned before code is written (Spec/Skill-Driven Development).

2026-06-29
Showing top 8 of 11 collected skills in this repository.
Showing 2 of 2 repositories
All repositories loaded