Showing 27601–27630 of 77205 skills
Soạn đề thi kết thúc học phần đại học kèm đáp án, thang điểm 10, ma trận phủ CLO và đề tương đương; tự luận, trắc nghiệm, vấn đáp. Dùng khi nói "ra đề thi học phần", "đề thi cuối kỳ", "đề có đáp án".
mochistudio-vn/kitviet
Lập kế hoạch chủ đề hoạt động trải nghiệm, hướng nghiệp theo GDPT 2018: sinh hoạt dưới cờ, sinh hoạt lớp, hoạt động chủ đề, có an toàn. Dùng khi nói "hoạt động trải nghiệm", "HĐTN", "hướng nghiệp".
mochistudio-vn/kitviet
Hướng dẫn khóa luận, đồ án: lịch theo tuần, duyệt đề cương, nhật ký gặp sinh viên, phiếu nhận xét, rubric bảo vệ, kiểm đạo văn, khai báo AI. Dùng khi nói "hướng dẫn khóa luận", "chấm đồ án".
mochistudio-vn/kitviet
Hướng dẫn nhóm sinh viên nghiên cứu khoa học: chọn đề tài vừa sức, phân vai, lịch, báo cáo tiến độ, dự thi giải thưởng, liêm chính, khai báo AI. Dùng khi nói "hướng dẫn sinh viên NCKH".
mochistudio-vn/kitviet
Phân tích khảo sát lấy ý kiến người học về học phần, giảng viên: điểm trung bình, tỷ lệ đồng ý, gom ý kiến mở, ẩn danh, kế hoạch cải tiến. Dùng khi nói "khảo sát sinh viên", "lấy ý kiến người học".
mochistudio-vn/kitviet
Phân tích nhu cầu đào tạo (TNA) 3 cấp tổ chức - công việc - cá nhân: khoảng cách năng lực có bằng chứng, tách vấn đề đào tạo giải được, xếp ưu tiên. Dùng khi nói "TNA", "nhu cầu đào tạo năm".
mochistudio-vn/kitviet
Thiết kế khóa học cho người đi làm theo ADDIE: mục tiêu đo được, module, tỷ lệ thực hành, hoạt động, đánh giá gắn Kirkpatrick, hậu cần. Dùng khi nói "thiết kế khóa học", "ADDIE", "đề cương khóa".
mochistudio-vn/kitviet
Soạn thuyết minh đề tài khoa học cấp cơ sở theo mẫu của trường: cấp thiết, tổng quan có nguồn, mục tiêu, nội dung, sản phẩm, tiến độ, dự toán. Dùng khi nói "đăng ký đề tài cấp trường".
mochistudio-vn/kitviet
Quy trình GVCN xử lý bắt nạt (cả trên mạng), xung đột, vi phạm, học sinh khủng hoảng tâm lý, nghi bị bạo hành: ghi nhận, báo cáo, phối hợp. Dùng khi nói "học sinh bị bắt nạt", "xử lý tình huống".
mochistudio-vn/kitviet
Develop and direct female-audience AI short dramas through role-specific workflows for showrunning, screenwriting, casting and original character design, art, performance, cinematography, storyboarding, sound, post, continuity, and asset handoff. Use when the user asks for 女频短剧、微短剧、言情或非言情女性向故事、女主成长、关系戏、职业戏、女性群像、选题、剧本、改稿、选角定妆、分镜运镜、生图/生视频制作说明、项目圣经或跨工种协作。
doublesq97-ui/su-ai-short-drama
Develop and direct male-audience AI short dramas through role-specific workflows for showrunning, screenwriting, casting and original character design, art, performance, cinematography, storyboarding, sound, post, continuity, and asset handoff. Use when the user asks for 男频短剧、微短剧、玄幻修仙、都市逆袭、职业创业、历史权谋、末世科幻、悬疑规则、竞技成长、选题、剧本、改稿、选角定妆、分镜运镜、生图/生视频制作说明、项目圣经或跨工种协作。
doublesq97-ui/su-ai-short-drama
Design and review predictable public APIs for TypeScript, JavaScript, React, and React Native libraries. Use when shaping exported functions, classes, hooks, options objects, event and listener APIs, error behavior, naming, cross-platform abstractions, or JS-only packages. Pair with build-nitro-modules when the library is backed by Nitro.
Doko-Demo-Doa/react-native-pdf-editor
Builds and designs React Native Nitro Modules with Nitrogen, HybridObject TypeScript specs, generated native implementations, zero-copy and native-state APIs, Swift/Kotlin/C++ bindings, example apps, and testing. Use when creating a Nitro Module, adding or reviewing HybridObjects, designing Nitro-specific public APIs, implementing native functionality, or setting up the nitrogen codegen pipeline. Pair with api-design for general library API shape.
Doko-Demo-Doa/react-native-pdf-editor
Design, implement, and review Kotlin and Android APIs. Use when working on .kt files, Kotlin nullability, sealed classes/interfaces, coroutines, Android threading, Java interop, or Kotlin-backed React Native Nitro Module implementations.
Doko-Demo-Doa/react-native-pdf-editor
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
Doko-Demo-Doa/react-native-pdf-editor
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
Doko-Demo-Doa/react-native-pdf-editor
Design, implement, and review Swift APIs and Apple-platform code. Use when working on .swift files, Swift types, Foundation or AVFoundation APIs, DispatchQueue, async/await, Task, actors, MainActor, thread-affine state, or Swift-backed React Native Nitro Module implementations.
Doko-Demo-Doa/react-native-pdf-editor
Upgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x to 0.y, or migrating Expo SDK alongside a React Native upgrade.
Doko-Demo-Doa/react-native-pdf-editor
Use this skill whenever you are about to build or change code. It builds safe-by-default from the project's charter and the defensive security knowledge the work touches, then checks the result.
wellwelwel/lagune
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
ash1794/vibe-engineering
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
ash1794/vibe-engineering
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
ash1794/vibe-engineering
Extracts and records architectural decisions from diffs, conversation context, and explicit choices. Supports automatic extraction from staged changes, deduplication against prior decisions, and persistent ADR-format logging with spec traceability. Use after a significant design or architecture choice, before committing a diff that embeds implicit decisions, or when the same question keeps resurfacing.
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass. Use when implementing or changing a parser, or any code that ingests user input, webhook payloads, API responses, or file formats.
ash1794/vibe-engineering
Assesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus. Use before a production launch, after a major refactor, when inheriting a codebase, or when someone asks how done the project is.
ash1794/vibe-engineering
Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog.
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism. Use when a task has 5+ subtasks touching independent files, or the user asks to speed up or parallelize the work.
ash1794/vibe-engineering
Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done.
ash1794/vibe-engineering